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

Tony Hoyle tmh at nodomain.org
Thu Aug 12 13:37:37 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.


On Thu, 12 Aug 2004 14:15:20 +0200, Oliver Giesen <ogware at gmx.net>
wrote:

>Axel Eckenberger wrote:
>
>> One last question on that
>> subject is the feature not working by design or by error - just out of
>> interest.
>
>As far as I know it _is_ working. You just couldn't use zeros in the 
>second figure (i.e. forcing rev. 2.1 should work). Zeros in revision 
>numbers are internally used for the so-called "magic branch numbers" 
>(you should be able to look that up in the Cederqvist, too) and are 
>therefore syntactically forbidden. At least that's how I understood and 
>handled this so far.
>
No, it broke (the attempt to resurrect the floating branches broke
it).  -r doesn't work at all at the moment.

The fix is simple enough this time so I've put it in.  

Eventually I want to move away from numeric revisions completely but
have held off because the frontends tend to use/display them (you can
resolve any file as <branch>.<version> eg. HEAD.1, development.24,
etc. which hides the internal numbers completely).

Tony




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