[cvsnt] Long version numbers | Tedious to keep track

Mike Wake mike.wake at thales-tts.com
Wed Mar 2 10:53:10 GMT 2005


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.


You could copy/merge your code base back to the HEAD.

Swaroop George wrote:
> Hi,
> I am experiencing a peculiar problem. Ours is a huge project and had
> multiple enhancement versions going in since live. Inaddition, we have
> monthly maintenance release as well as patch releases on an as needed
> basis. All this led us creating multiple branches to the code base.
> And the version numbers have now become as long as 1.2.2.1.2.1.2.1 and
> quite cumbersome to handle.
> 
> - Is there anyway of alternate versioning and making it much more
> simple, but still maintaining the history to an extent.
> - How about creating a fresh root after archiving the current code to a backup?
> 
> Bright ideas are welcome..
> 
> Thanks in advance
> Swaroop
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs



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