Re: first change on a branch causes no change to show up in -rTAGA::TAGB

[Todd Denniston]

Matthew Herrmann wrote:
> 
> Hi All,
> 
> I'm using cvs2cl to generate version differences on branches, but I'm having
> trouble with picking up changes where no change was previously there. I
> think the problem is one in cvs log, though, not cvs2cl.
> 
> Here's the command I use
> 
> cvs2cl -w -f ChangeLog_%1_To_%2.txt -r%1::%2
> 
> the scenario that breaks it is:
> 
> working on branch BRANCH1
> 
> at TAG1, on BRANCH1 : file is on 1.23
> at TAG2, on BRANCH1 file is on 1.23.1.4 after changes
> 
> the problem is that even when looking at 2 tags on the same branch, it is
> only after the first change to the file that it becomes _really_ on the
> branch, before that, the tag is still officially on the trunk.
> 
> What would fix this for me is for 1.23 => 1.23.x.y to be considered on the
> same line. At the moment the line is only being start just after 1.23 which
> means I'm losing a significant number of changes out of these history logs.
> 
> are there any patches available for this problem? some others must have had
> this problem with log -r.
> 
> cheers,
> matt
I assume you are speaking of either
http://search.cpan.org/author/FLUFFY/CVSUtils-1.00/
or http://www.red-bean.com/cvs2cl/

the '-r' option to cvs2cl is for:
[-r, --revisions              Show revision numbers in output]

what I think you want is to pass options to cvs log so you should use -l
"options":
[-l OPTS, --log-opts OPTS     Invoke like this "cvs ... log OPTS"]

if you want to pass revisions to cvs log I believe it should be something like

cvs2cl -l "-r%1::%2" -w -f ChangeLog_%1_To_%2.txt 

I use the global compress option as 
cvs2cl.pl -g "-z9" -r -t -f cl.txt
so I think the line I gave you above will work, if cvs log will accept whatever
"-r%1::%2" evaluates to.

-- 
I'd crawl over an acre of 'Visual This++' and 'Integrated Development
That' to get to gcc, Emacs, and gdb.  Thank you.
        -- Vance Petree, Virginia Power