Re: Info-cvs Digest, Vol 19, Issue 17

2004-06-08 Thread Bret A Cooper 

Hello,

* On Mon, Jun 07, 2004 at 05:34:02PM -0400 Larry Jones wrote:

  However, I now believe its not that simple, as the binary
  files(only) must be initialized with the -kb option. Is
that
  correct? If so, any suggestions on the simplest/easiest to
go about
  this?
 
 If you can distinguish the binary files from the text files by
their
 names (e.g., *.gif files are always binary), you can use the CVS
 wrappers facility to automatically handle the files correctly


To add to this: If the text files are Unix-style (LF only), I also
had
success in importing everything as binary, and changing the text files
to text afterwards with cvs admin.

If the text files are Windows style, doing a dos2unix on them, and
then
treating it as in the above case, works, too.

Best regards,

  Spiro.

Spiro,
Thanks for your reponse. It prompts
a couple more questions. When you went back and ran the
cvs admin command, did you
have to run it once for every file you wanted to change?
Also, would it work equally well to
put all the files in as regular files and the run cvs admin
later
to change the binary files?

ThanksBret Cooper
IBM Global Services - ATT ADM Account
614.501.2540___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

Re: Info-cvs Digest, Vol 19, Issue 17

2004-06-08 Thread Spiro Trikaliotis 
Hello Bret,

* On Tue, Jun 08, 2004 at 01:50:36PM -0400 Bret A Cooper wrote:
 
 Thanks for your reponse.  It prompts a couple more questions.  When
 you went back and ran the cvs admin command, did you have to run it
 once for every file you wanted to change?

Yes, this has to be run for every file to be changed. Anyway, you can
use wildcards, so a

cvs admin -kk *.c *.cc *.h makefile

and so on works very good.

Even if you forget to change a file to text mode, it does not do much
harm, as you can even do this afterwards.


 Also, would it work equally well to put all the files in as regular
 files and the run cvs admin later to change the binary files?

It depends upon your binary files. If 

1. your client runs Windows (CR/LF instead of LF), or
2. you binary files contain any of the RCS keywords ($Id$, $Log$, etc),
3. not sure if there are other conditions which could do havoc to your
   binary files,

chances are very good your binary files will get corrupted, and you will
not be able to recover them from CVS. Thus, checking everything in as
binary is a more defensive solution than the opposite.

Regards,
   Spiro.

-- 
Spiro R. Trikaliotis I'm subscribed to the mailing lists I'm posting,
http://www.trikaliotis.net/  so please refrain from Cc:ing me. Thank you.


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs