Re: cvs log and revision range

[Laine Stump]

address@hidden (Larry Jones) writes:

> Thierry Leconte writes:
> > 
> > Now I want to know all changes between two symbolic tags.
> > cvs log must do the job, but if, for some files, the 2 revisions
> > coresponding
> > to the 2 tags are on different branch cvs log will not work properly.
> > 
> > This is in the FAQ, but I wonder why cvs log could not handle this case
> > :
> >  is it a well know bug that nobody have time to fix or is there a more
> > serious reason ?
> 
> "Between" really isn't meaningful for revisions on different branches.

Sure it is, you just have to think about it a bit differently. It
could be displayed as a set of "reverse logs" going from the first tag
backwards to the common branchpoint, then "forward logs" to the 2nd
tag. Bonus points could be added for detected "reverse" and "forward"
revisions that cancelled each other out (could be done by comparing
the diffs of each revision, but would fail if there were any small
branch-specific changes in one or the other). I'm not sure how the
reverse logs could be displayed in the output - perhaps with "-" at
the beginning of every line or something...