Subject: Re: rcs, ci, co, et al
To: None <firstname.lastname@example.org>
From: Greg A. Woods <email@example.com>
Date: 12/11/1998 00:15:53
[ On Thu, December 10, 1998 at 23:46:33 (-0500), Andrew Brown wrote: ]
> Subject: Re: rcs, ci, co, et al
> >> it *is* controlled by rcs (that's the problem) but not *my* rcs. the
> >> keywords are from other contexts that i'd prefer to leave intact.
> >"rcs -kb" or "rcs -ko" should work with your case, I believe.
> >"ci" doesn't touch the keywords, "co" touches the keywords.
> >So, If you do "co -ko ..." (or "co -kb"), the file you got is exactly
> >same as the file you checked-in. If you do "rcs -ko ...", then default
> >behaviour of "co" is changed to "co -ko".
> >hope this helps.
> but rcs and co are not effective on a file that's not already in *my*
> rcs repository. and after i do the initial check-in, the keywords get
Oh, now I see what you mean.
Running "rcs -ko", or using "co -ko" will ensure that the "original"
keywords are used when the file is checked out.
(I use "cvs co -ko" all the time with vendor-branched CVS modules for
the same reason)
Greg A. Woods
+1 416 218-0098 VE3TCP <firstname.lastname@example.org> <robohack!woods>
Planix, Inc. <email@example.com>; Secrets of the Weird <firstname.lastname@example.org>