On Sat, 18 Nov 2006, Les Mikesell wrote:
> > 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.
Me too. Checking out a specific revision (or updating to a specific
revision), testing it, and then copying it, will give you that, while
also avoiding a mixed-revision copy.
You seem to have the idea that I was advocating making tags from things
that had not been tested. I have no idea where you got that idea. I
advocate making tags from things that have been tested and that also
share the same revision number.
> 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?
Simply that it makes the history easier to follow. I don't want
somebody in the future to waste time wondering why a tag was made from
mixed revisions instead of a single revision.
If there really is a good reason for the tag to be made from mixed
revisions, I think that it should be clearly documented in the commit
log.
> 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
> just tagged.
Yes, that's another way of achieving the same result.
--apb (Alan Barrett)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Nov 18 09:02:22 2006