On Sat, 2006-11-18 at 01:02, Alan Barrett wrote:
> On Sat, 18 Nov 2006, Les Mikesell wrote:
> > Back up to the previous example where it was considered a problem
> > that a user might commit his change, then someone else might commit
> > before he copied to a tag, and copying the revision number given by
> > his commit to a tag was suggested as a solution. What if someone else
> > did their commit just before this user instead? The tag still ends up
> > including something he doesn't know about.
> You would have got (or will soon get) the commit email reporting the
> other person's change. You can browse the commit logs. You might or
> might not have got a "WC is out of date" error when you committed.
And the cycle may still repeat before you catch up.
> > If you make the tag from the working copy you know (and perhaps even
> > have tested...) exactly what is there.
> Fair point. But I'd still prefer to do the testing with a
> non-mixed-revision WC, and do an URL to URL copy.
Why? I'd much rather have, for example, a release tag applied
to the actual contents of a QA working/tested copy than
whatever happens to have subsequently been dumped on the
trunk. That is, the reason I'd want to apply a tag is
always to identify a state known to work together, not
just known to already exist at the head together. If changes
have been made locally to that working copy I'd probably
also want to commit them back to the trunk, but that's
a separate decision. If other changes have been added to the
trunk at that point, making this a mixed revision, that is
really irrelevant to the release build that I want to match
this working copy exactly. What's the point of a tag being
a fully-functional copy in its own right if you insist on
it being a duplicate of some other revision state?
And in any case, if you want to insist on the WC not being
mixed-rev at the time you tag, you have the option to commit
and update before tagging, then still tag from the WC. At
least you can then claim to know something about what you
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Nov 18 08:27:57 2006