"Cameron, Steve" wrote:
[ DELETED STUFF ]
> HEAD as described here definitely has some impossible
> or at least meaningless cases: for instance, a sticky,
> non-branch tag (or date or revision) on a file could
> match a revision that is present on multiple branches,
> so which is the "correct" current branch for which the
> tip revision should be found? There's no sensible answer.
> I suppose that could be treated as an error and CVS
> could say, in essence, "you've asked me a nonsense
> question." for such files. Seems more trouble than
> it's worth to me though.
I think my approach would be that non-branch tags would be treated as the top
of a branch with no revisions commited to it. Therefore, for a file that is
checked out on the non-branch tag, the difference between it and HEAD would
be empty.
Now for a file that has not been checked out with a tag, I think the
difference would have to be against the top of the trunk.
