Hi Everyone,
This is to let you know that I have just tried out the development version
of cvs post Larry's latest fix to log.c, and i'm now getting spot-on
tag-to-tag version histories using cvs2cl, including when the tags are on
branches.
So it gets the big thumbs up from me!
Thanks Larry.
Hi All,
I have taken Larry's suggestion and installed the latest dev version and it
is better, but still not 100%.
Here is the problem I found on development version of CVS:
For a file, FILE1:
Tags:
=
TAG2:
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
Matthew Herrmann writes:
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.
I believe that's fixed in the current
oops sorry Larry, just saw your post after I sent my reply.
thanks for the input Larry and Todd, I'll upgrade asap.
-Original Message-
From: Matthew Herrmann [mailto:matt;faredge.com.au]
Sent: Thursday, 14 November 2002 10:27
To: Todd Denniston
Cc: CVS Mailing List
Subject: RE: first
Thanks todd, but with this option I see the exact behaviour.
The problem, as I verified is that the -rTAG1::TAG2 option
will not output any revisions when TAG1 and TAG2 are not on the same
branch.
cvs log -rBRANCHTAG1::BRANCHTAG2 main\Main.bas
What is frustrating about this is that these tags
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
