Re: Updating revision number on a branch.

[Heather]

Okay, thanks for your quick repy!  We were aware that this was
basically a 'cosmetic' fix.  We print the CVS log entries in the header
of the files to easily see our changes, so we're seeing the 1.7.2.XXX,
etc and wanted to 'clean it up' a bit so it was easier to read.

I take it we can still go ahead and do this on the main trunk?  We have
some files getting up to version 1.102 etc so it'd be nice to be able
to start this latest version with the new revision number if that makes
sense.




Jim.Hyslop wrote:
> Heather wrote:
> > We are doing parallel development with 2 different versions of our
> > code.  We have version 2 on a branch and version 3 is on our main
> > trunk.  What we want to do is update the revision numbers on the
> > version 2 branch to be 2.xx and the revision numbers on the version
3
> > trunk to be 3.xx.
> No, you don't :=)
>
> Managing revision numbers should be considered a black box to you and
me -
> let the program handle the revision numbers. Handle what you need
through
> symbolic tags - they are much simpler to manage, and much more
intuitive.
>
> > Is this possible?
> Actually, no it's not, because of the way CVS manages its revision
numbers.
> If you _really_ want the gory details, you can refer to
> https://www.cvshome.org/docs/manual/cvs-1.11.18/cvs_5.html#SEC58.
>
> --
> Jim Hyslop
> Senior Software Designer
> Leitch Technology International Inc. ( http://www.leitch.com )
> Columnist, C/C++ Users Journal ( http://www.cuj.com/experts )