On Sat, 18 Nov 2006, Les Mikesell wrote:
> > 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.
>
> That only works if you make no changes and tag the revision
> number from your checkout or last update - or you are lucky...
> If you make a change and commit it back, someone else may
> have made other changes already.
Your workflow is clearly different from mine. If my role is testing and
tagging, then I will not be making changes and committing them; I'll be
checking out a specified revision (probably from a stable branch with a
low commit rate), testing it, and tagging it if it's good; perhaps I'll
also update a version number and commit that. If my role is developing
the trunk, I won't be tagging. If my role is updating a stable branch,
I'll be aware when tagging is imminent, and try not to break it.
If, in my testing role, I find that I am forced to use mixed revisions,
I'll make that clear in the log message when the tag is committed, but
I'd expect that to be rare (apart from updating a version number).
--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 20:32:40 2006