Michael Gersten
> > You're right. For consistency's sake, "cvs up -C file" should get a
> clean copy
> > of the HEAD. I think, in general, there should be a way to specify the
> base
> > revision (is there a BASE alias similar to HEAD?)
>
> Ok, since HEAD means different things, etc, I'd like to propose the
> following alias tags:
[smc] BTW, there is a similar proposal in cvs.texinfo,
but using different names, names that begin with ".", so
as to be guaranteed not to conflict with exiting tags...but
this might be more difficult to implement.
> TRUNK - top of the trunk
[smc] I may have a patch that does exactly this.
I say "may", because I haven't done extensive
testing, and I implemented it by copying the code
for HEAD, but fixing the part where HEAD differed
for "cvs diff". So if HEAD is broken in other ways
besides the "cvs diff" case, then my TRUNK patch
would be broken in the same ways. However, I do
not know that it is broken.
> BHEAD - head of the current branch (or trunk if not on a branch)
> PHEAD - head of the parent branch (or trunk if the file split from the
> trunk)
>
[smc] possible? (see comments under SPLIT...)
> TBASE - point at which this file left the trunk. Same as self if not on a
> branch.
> (Essentially, base back at the trunk)
> SPLIT - point at which this file left was branched. Same as self if not on
> a branch.
> (Essentially, base of this branch).
[smc] Is this possible? When I create a branch,
I always do something like this..
cvs rtag branch_origin everything
or cvs rtag -r some_branch_tag branch_origin
everything
cvs rtag -b -r branch_origin branch_tag everything.
I once tried to figure out an algorithm for coming up with
the revisions that made up "branch_origin" in case I forgot
to create this tag, using only "branch_tag". I convinced
myself that it couldn't be done...(well as soon as you say
something like that someone will figure out how to do it.)
Anyway, this SPLIT seems like the same problem, so I'm
wondering if it's possible. I forget now how I convinced
myself finding a lost branch_origin type tag was not
possible in all cases... Something to do with the fact
that CVS doesn't actually create a new revision at the
time a branch is created, but only when changes are
committed to that branch.
[...]
-- steve
