Chris Deever wrote:
> Is there a way to check out a branch such that CVS retrieves the branch as
> it was before any new changes were committed to it? Alternatively, is
there
> a way to determine the date on which a branch was created? I have tags
from
> the same time period that the branch was created, so also if it is
possible
> to find the date that a branch was created, I could use a tag from the
main
> trunk to get the same info.
>
> Basically, I would like create a list of all log comments of all changes
> that were committed to the main trunk since the time the branch was
created,
> so that I can double check that all changes made in the trunk are properly
> applied/merged to the branch.
I have a patch to CVS that might help do what you want.
It's at http://www.geocities.com/dotslashstar/branch_patch.html
It applies to the latest development version of CVS as of 7/9/2000.
(Haven't tried
it lately though.)
With this patch, you can use a tag like "branchname.origin" to mean the
start of a branch. so you could do:
cvs rdiff -u -r branchname.origin -r branchname modulename
to get all the diffs made to the branch.
There might be one hitch though, I can't remember for sure.
(I have to try this tonight to find out for sure).
The patch works by trying to find the first revision of each file on the
branch.
So if a branch is created, then files are added to the branch, those added
files
are counted as being part of the "origin" of the branch regardless of _when_
they were added. However, I do seem to remember that when adding files to a
branch,
a dead revision is added to the branch first, in which case this would work
correctly, and my fears are unfounded. I just mention it so you can watch
out for it. I think the problem really occurs only when you use
".trunk.origin",
because when you add files to the trunk, a dead revision is not added
first...
(and by this symptom, I begin to think that ".trunk.origin" is somewhat
nonsensical anyway, or logically should always be the empty set or
something.)
Let me know if you find any problems with my patch.
-- steve
