Re: Is label support in future release?

On Mon, 2006-11-20 at 01:38, Alan Barrett wrote:

> > The part I'm having trouble with is how to permit ongoing concurrent
> > development in the repository beyond the workspace copy containing the
> > 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

That's not an interesting scenario because you don't
make changes. The one we are discussing is:

You: svn checkout url://repository/project/trunk
You: change file(s)
Other people: commit more stuff - that you don't want now -
You: commit changes
You: decide what you have is good for testing
You: svn copy -m 'create tag foo for testing' \
                . url://repository/project/tags/foo

At this point you have what you want in the copy, and
the trunk also includes your changes, but no revision on
the trunk is an exact match for the tag.

> [Remainder snipped. This thread is much too long.]

Sorry, but it is long because you suggested that the
above scenario is not the best practice and still have
not explained either the problem it poses or a better
approach. I do see the possibility of an error by
forgetting to commit to the trunk, but I can't see
how that goes away even if you do the extra steps to
make your own branch.

-- 
  Les Mikesell
   lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org