Re: help with rlog

[Larry Jones]

sreekanth writes:
> 
>     I have a tree that's imported .Let 's say i have a file "file1" with 
> initial version 1.1.1.1 (yes, that's the revision i have for all the files 
> that are imported), Now create a tag RLS_TAG1 on it. Then commit the next 
> version of it, now the revision number is 1.2(strange for me, but still). 
> Now i do a tag RLS_TAG2. Now if i do a rlog of messages between RLS_TAG1 and 
> RLS_TAG2 using command
> cvs rlog -rRLS_TAG1::RLS_TAG2 <path>file1,
>  I was expecting the log message of the commit message that i just did(of 
> revision 1.2) , but instead i see the original commit message that was used 
> to Import this file into the tree(revision 1.1.1.1), Is that an expected 
> behaviour?

Yes, I'm afraid so.  The problem is that CVS doesn't keep track of the
relationship between revisions on the vendor branch and revisions on the
trunk.  As far as it knows, 1.1.1.1 and 1.2 are completely unrelated, so
it's meaningless to ask for the changes between them (it goes ahead and
does *something* rather than just refusing to do anything, but what it
does isn't particularly useful).

-Larry Jones

Whatever it is, it's driving me crazy! -- Calvin