[Top][All Lists]

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

Re: Need help with -kk, -kb, etc

From: David L. Martin
Subject: Re: Need help with -kk, -kb, etc
Date: Thu, 2 Aug 2001 21:37:28 -0500


Check the cvs-info archives for December, 2000 available at
and search for the thread entitled "Proposal to fix CVS binary
file implementation." 

The solution that worked for me was to patch the CVS code
to never allow a command-line override of -kb if
assigned to an archive.

I notice that the patch I submitted is mangled a bit in the mail
archive file, so I've attached it here again.  It applies to the
cvs-1.11 version of vers_ts.c


----- Original Message ----- 
From: "Paul D. Schmidt" <address@hidden>
To: <address@hidden>
Sent: Monday, July 30, 2001 12:38 PM
Subject: Need help with -kk, -kb, etc

> Our company uses the -kk option in our Makefiles to prevent
> keyword expansion, as that causes conflicts with merges.
> The problem is that this option is sticky, and gets used for
> added files.  Not only is it sticky, but it also overrides the
> -kb option since we use -kk on the command line...
> For example, if someone adds a .jar file and specifies it to be
> added with -kb, it's checked out with -kk and not -kb when -kk is
> (automatically, for all files) specified on the command line.
> (-kk is not added to the command line for "production build mode"
> since we don't need to worry about merges, and actually want the
> $Id$, etc tags in there)
> What is the best way to resolve this situation?  Any advice how
> we could better manage our repository would be greatly appreciated.
> Thanks,
> -Paul
> --
> [Paul D. address@hidden
> [Xtime, Inc................][........]
> "Everybody keeps saying that women are smarter than men, but did
>  you ever see a man wearing a shirt that buttons down the back?"
>                                  --Anonymous
> _______________________________________________
> Info-cvs mailing list
> address@hidden

Attachment: patch.txt
Description: Text document

reply via email to

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