Hi Larry,
Larry Jones schrieb:
> Martin Roehrig writes:
> >
> > To solve the problems and misunderstandings around this subject, what do you
> > think about introducing a new built-in tag (say TRUNK) that does the same for the
> > main trunk as a branch tag does for the branch (or should do...), namely always
> > refer to the latest revision on the main trunk (TRUNK) resp. branch (branch tag),
> > consistently in all suitable cvs commands? (I hope my understanding of branch
> > tags is correct so far.)
>
> The obvious alternative is to change HEAD to mean that (which, if I
> understand the current state of things, it already does everywhere
> except for diff).
My suggestion went even a bit further:
Martin Roehrig schrieb:
> HEAD should then always refer to the latest revision in the branch resp main
> trunk the current working copy is based on and therefore it should not be allowed
> in cvs commands that directly work on the repository (like rdiff - don't know if
> it is already forbidden there).
Thus you have TRUNK as an analogue to the branch tags (i.e. it always refers to the
main trunk) and you have HEAD which refers to the latest revision of the current
"development line" (be it a real branch or be it the main trunk) as denominated by the
working directory where the cvs command using the HEAD tag is called.
I think that might be useful in some cases, e.g. when comparing the working copy to the
latest state of the same branch in the repository. Then you wouldn't have to look what
branch the working copy was based on. You could even write a one-line script that would
do that job in whatever working directory it were called.
Best regards
Martin
