Re: Explicit revision numbers

[Holger]

Mark D. Baushke wrote:
> If someone has done a 'cvs admin -o1.23' after revision 1.24 exists,
> then your script will do the wrong thing as the predecessor revision
> will be 1.22 rather than 1.23. This of course is concerned with finding
> the predecessor of revisions that already exist in the repository.
>
> > My question:
> > IRC I've read somewhere that you are able to explicitely specify new
> > revision number - e.g bump the major number - when checking in. Is this
> > still true?
>
> Probably, but do not use it. CVS revision numbers are for use by CVS
> internals and it is entirely possible to break fundamental assumptions
> when you try to do tricky things with them.
>
> > Is there a better way than the above to figure prevrev out?
>
> Better? I suppose that depends on what you mean. You could process
>
>   cvs rlog -N -r:1.24 module/subdir/filename

I tried this - but it does not tell you what the previous version is.

My conclusion is that it is not possible with the current CVS
functionality to reliably determine the previous version. And the best
shot I have is the algoritm described in previous post - depending on
my fellow CVS users to not manipulate the revision numbers.
Oh well, as you wrote, people should leave the versioning to the
internals of CVS. And I'll have to rely on that.

Thank you.

Holger