[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: How to change keyword substitution option
From: |
Mike Ayers |
Subject: |
RE: How to change keyword substitution option |
Date: |
Fri, 18 Apr 2003 10:31:56 -0700 |
> From: Larry Jones [mailto:address@hidden
> Sent: Friday, April 18, 2003 10:07 AM
> address@hidden writes:
> >
> > I have erroneously imported a lot of C source files with
> the -kb option. I
> > realized this error only after a lot of modification on that files.
> > Does somebody know how to change the option to text, so
> that the $log$
> > keyword substitution works ?
>
> IF (and that's a big "if") you're lucky enough to be working
> on systems
> that do not differentiate between text and binary files (Unix
> and Linux,
> for example, do not; Windows does),
Windows does not distinguish between text and binary files. It does,
however, use a different line ending than CVS' canonical line ending, which is
the Unix line ending.
> then all you have to do
> is use admin
> -kkv to change the repository files and then update -kkv to
> update your
> working directory. If your system *does* distinguish, then you have a
> much more complicated process ahead of you. Probably the
> easiest way to
> fix it would be to use admin -kkv as above to change the repository
> files, edit the CVS/Entries file(s) in your working directory
> to remove
> the -kb from each line, touch all of the files to update their
> modification times, then do a commit.
If, however, these were borught in by import, as claimed, then there
are some much simpler methods available. The easiest is to check out two fresh
copies of the module. In the first copy, `cvs rm` each file in the import
tree, then commit it all. In the second tree, remove all the CVS directories,
then reimport the tree without the binary flag. If you use a different vendor
name, then everything should look to all appearances as if the bad import never
happened.
/|/|ike