> Martin Roehrig writes:
>
[...]
> > 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.
[smc] "TRUNK" sounds useful, "HEAD" as
described here, less so, since the branch
tag may currently be used for that purpose,
(though it might be useful for scripts or
something that don't want to have to
know what the branch tag is, or in the case
of some kind of hybrid sandbox with
modules from multiple branches (or even
multiple repositorires?))
But, does anyone here know how to
implement either HEAD or TRUNK as
described here? ,, I don't know how.
Well, perhaps someone does...
But, if not, the other option, making HEAD at
least be consistently interpreted by
"cvs diff" seems better than the status
quo, and that we do know how to do.
-- steve
