Larry Jones a �crit :
>
> 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.
between branch for sure, but between main trunc and a branch it is :
if you do :
cvs log -r1.30:1.30.2.6 test.c
you could expect to get all the commit that lead to 1.30.2.6 from 1.30,
but
cvs log just list all the commit of the file ! , for me it's a bug
It's sure that the semantic of something like :
cvs log -r1.30.2.8:1.30.4.6 test.c
is more questionable.
I propose to list all the commit from 1.30 to 1.30.4.6 , I mean
the commit from the common ancestor to the upper branch...
I have take a look at log.c and I hope to finish the mods today
Do you know where to send patches ?
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
