[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gnugo-devel] Lack of files in CVS \gnugo\patterns\

From: bump
Subject: Re: [gnugo-devel] Lack of files in CVS \gnugo\patterns\
Date: Wed, 4 Dec 2002 15:18:59 -0800

> Remember, however, that CVS is not the only way to retrieve the
> DSP & DSW files.  These files are also available through .tar.gz files
> off the web site.  There is no conversion performed on these files -
> they are pulled directly out of the repository w/out any conversion.

Right, if we removed the carriage returns from these files, then 
they'll be wrong in the tarballs unless I do something complicated
at my end.

If you correct these files once (copy them out of the tarball, or
strip the extra CR by another method), they will not get
overwritten when you run cvs update. CVS update will report
a merge, but the file will not be change.

Of course you will have to do something when a .dsp file is
changed, which tends to happen when we add a .c file to the

>From the CVS manual:

>    The `-kb' option available with some CVS commands insures that
> neither line ending conversion nor keyword expansion will be
> done.

That sounds good ... no line ending conversion.

>    Here is an example of how you can create a new file using the `-kb'
> flag:
>      $ echo '$Id$' > kotest
>      $ cvs add -kb -m"A test file" kotest
>      $ cvs ci -m"First checkin; contains a keyword" kotest
>    If a file accidentally gets added without `-kb', one can use the
> `cvs admin' command to recover.  For example:
>      $ echo '$Id$' > kotest
>      $ cvs add -m"A test file" kotest
>      $ cvs ci -m"First checkin; contains a keyword" kotest
>      $ cvs admin -kb kotest
>      $ cvs update -A kotest
>      # For non-unix systems:
>      # Copy in a good copy of the file from outside CVS
>      $ cvs commit -m "make it binary" kotest

Is this what we want to do?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]