[cvsnt] Sticky option (-ko) permanent or only on in working directory?

Nick Duane nickdu at msn.com
Fri Aug 18 16:17:06 BST 2006

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

"Tony Hoyle" <tony.hoyle at march-hare.com> wrote in message 
news:ec4bgb$obg$1 at paris.nodomain.org...
> Nick Duane wrote:
>> But the keyword is still getting expanded in this file.  I can't figure 
>> it out as it seemed as if things were working ok locally, but maybe it 
>> just
> The 3rd party file probably already contains expanded keywords.  If you 
> set -ko on a revision it simply stops any further expansion from that 
> revision onwards.
>> expanded.  I wanted to be able to selectively turn off keyword expansion 
>> on certain files and have it stay that way.  At this point I'm going to 
>> edit
> This is exactly how it works.

I'm about to start pulling my hair out.  I still get this to do what I want 
to do.  I did the following.

* First I deleted my sandbox.  I then checked out the root level module.  I 
checked the files in question.  They all had Header and Log keywords set for 
my checkin.
* cvs update -ko <file>
* cvs commit -m "..." <file>
* copy original file back into sandbox
* cvs commit -m "..." <file>

* I then check the file again.  It appears that it hasn't added to the 
Header or the Log so I think I've fixed the problem.

* delete sandbox
* checkout module
* check file again and notice that it does have my Header and Log info in 
the file.

What's going on?


More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook