1 |
On Sun, Apr 24, 2005 at 07:04:58PM -0700, Donnie Berkholz wrote: |
2 |
> Robin H. Johnson wrote: |
3 |
> > You aren't the first no, but the solutions to it are limited: |
4 |
> > - teach developers to use -kb where they should |
5 |
> Wouldn't it be -ko for a patch? |
6 |
-kb is actually better than -ko, due to how it's handled on later commits to a file. |
7 |
|
8 |
The CVS manual states: |
9 |
`-ko' |
10 |
Generate the old keyword string, present in the working file just before it was |
11 |
checked in. For example, for the Revision keyword, generate the string |
12 |
$Revision: 1.1 $ instead of $Revision: 5.7 $ if that is how the string appeared |
13 |
when the file was checked in. |
14 |
`-kb' |
15 |
Like `-ko', but also inhibit conversion of line endings between the canonical |
16 |
form in which they are stored in the repository (linefeed only), and the form |
17 |
appropriate to the operating system in use on the client. For systems, like |
18 |
unix, which use linefeed only to terminate lines, this is very similar to |
19 |
`-ko'. For more information on binary files, see Handling binary files. In CVS |
20 |
version 1.12.2 and later `-kb', as set by cvs add, cvs admin, or cvs import may |
21 |
not be overridden by a `-k' option specified on the command line. |
22 |
|
23 |
Note the last sentence again: |
24 |
In CVS version 1.12.2 and later `-kb', as set by cvs add, cvs admin, or cvs |
25 |
import may not be overridden by a `-k' option specified on the command line. |
26 |
|
27 |
So this makes it much harder to break on later revisions as compared to -ko. |
28 |
|
29 |
Also, if you have inconsistant linefeeds, cvs -ko can break sometimes (some |
30 |
versions of Outlook mangled patches in this way @%$&@%$^). |
31 |
|
32 |
-- |
33 |
Robin Hugh Johnson |
34 |
E-Mail : robbat2@××××××××××××××.net |
35 |
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 |
36 |
ICQ# : 30269588 or 41961639 |
37 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |