[cvsnt] Re: Increasing release with "commit -r" fails

Tony Hoyle tmh at nodomain.org
Thu Aug 12 00:44:04 BST 2004

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.

Axel Eckenberger wrote:

> C:\temp\test\DataProv\MDirProv2>cvs commit -m "none" -r 2.0 AssemblyInfo.cs
> Checking in AssemblyInfo.cs;
> cvs [commit aborted]: revision `2.0' does not exist

You can't do this.  2.0 is a 'reserved' number by RCS and you can't 
create a revision with that number anyway, plus you can't use commit -r 
to create it (import will create 2.x.x branches if it has to).

Don't use -r to specify revisions.  Revision numbers are internal to CVS 
and shouldn't changed.  Use tags to mark specific revisions instead.


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