[cvsnt] Re: Changing expansion option does not work in CVSNT

Oliver Koltermann okoltermann_deletethis_ at gmx.de
Wed Jun 7 10:41:48 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.

Hello Tony,

Tony Hoyle <tony.hoyle at march-hare.com> writes:
> A forced commit is necessary to change the expansion option of a
> revision, since it's something that you really don't want to happen
> accidentally (these things rarely change).
> update -k is a temporary change to the file expansion which is made
> permanent by commit -f.

shame on me, it's even documented for "commit -f":

  "This command is also used when changing -k expansion
  options. Unless -f is specified modified options will not be
  propogated back to the server."

Thank you for the help!

...but again I found something outdated in the documentation. The
example for "commit -f" reads:

   "If the current revision of file is 1.7, then the following two
   commands are equivalent:

   $ cvs commit -f file
   $ cvs commit -r 1.8 file"

As far as I know "commit -r" has been cancelled.

Best regards,
O. Koltermann

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