So what do I do??
I'm using CVS v1.11.1p1 compiled for Win32. I don't know whether that is
POSIX compliant or not? (or what that even means :). 
I thought that -ko stopped keyword expansion and -kb stopped both
keyword expansion and newline conversion. Will I lose any functionality
if I import my text sources into CVS with -kb?? I think that the reason
the binary files are being corrupted is because of the newline
conversion.

Thanks.

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf
Of
> Greg A. Woods
> Sent: Tuesday, 8 January 2002 4:48 PM
> To: Nicholas Catanchin
> Cc: [EMAIL PROTECTED]
> Subject: Re: Third-party binary files, keyword expansion probs.
> 
> [ On Tuesday, January 8, 2002 at 16:09:33 (+1000), Nicholas Catanchin
> wrote: ]
> > Subject: Third-party binary files, keyword expansion probs.
> >
> > Greg: In a message you wrote once you said:
> > "What you need to do is to _always_ check out your vendor branched
> > modules with the (sticky) '-ko' option.  In other word you basically
> > have to tell CVS to NEVER touch any keywords or their values in any
file
> > in your vendor branched module.  You really don't want to be messing
> > with another project's keyword values anyway."
> >
> > That is what I want to do - but -ko seems to corrupt my binary
files.
> 
> Hmmmm.... no doubt you're using some non-POSIX-compliant client.
Don't.
> 
> (you might be able to use both '-ko' and '-kb', though in theory '-kb'
> should imply '-ko')
> 
> --
>                                                               Greg A.
Woods
> 
> +1 416 218-0098;  <[EMAIL PROTECTED]>;  <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird
> <[EMAIL PROTECTED]>
> 
> _______________________________________________
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs


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

Reply via email to