Les Mikesell wrote:
> 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.
>
Your scenario is faulty.
You cannot directly commit since the the HEAD revision has
moved on due to the other people's commits. You first have
to update, and will thus include these other changes.
Greetings,
Gerco.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 21 15:00:29 2006