Alan Barrett writes:
> On Sun, 19 Nov 2006, Les Mikesell wrote:
> > The part I'm having trouble with is how to permit ongoing concurrent
> > development in the repository beyond the workspace copy containing > > state you want to tag.
>
> You don't need to do anything special to permit that; it just works.
>
> You: svn checkout -r 100 url://repository/project/trunk
> Other people: commit stuff
> You: test
> Other people: commit more stuff
> You: decide that test was successful
> You: svn copy -m 'create tag foo from trunk revision 100' \
> -r 100 url://repository/project/trunk \
> url://repository/project/tags/foo
This shows the problem with the current method. Why did you checkout
revision 100? Was it the head revision at the time? The main
repository I use is at around revision 20,000. A legacy repository is
also at about the same revision number. The revision number probably
increments by 10-20 each day.
I'd suggest instead:
You: svn copy -m 'create candidate tag foo on mm/dd/yyyy from trunk' \
url://repository/project/trunk \
url://repository/project/tags/foo.test
You: svn checkout url://repository/project/tags/foo.test
Other people: commit stuff
You: test
Other people: commit more stuff
You: decide that test was successful
You: svn move -m 'create tag foo of mm/dd/yyyy' \
url://repository/project/tags/foo.test \
url://repository/project/tags/foo
I'm not sure this is the exact case the original poster wanted, but I
would argue that the point of tagging and branching is that you always
work with tag / branch names, never with revision numbers.
Unfortunately the SVN book seems to assume that users routinely track
revision numbers when checking out and committing. Repository
revision numbers change too often for this to be practical.
Thomas Wicklund
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 20 19:35:56 2006