On Tue, 2006-11-21 at 15:00 +0100, Gerco Ballintijn wrote:
> >
> > 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.
No, please see the 'Mixed Revision Working Copies" section of
the svn book, expecially 'Updates and Commits are Separate'
followed by 'Mixed revisions are normal'. There are some
limits but it is a common occurrence when different people
work on different file in the same project concurrently and
it leads to many working copy states that you'd like to be
able to reproduce for testing or even release that don't and
can't exist as repository revisions because things you don't
want to include were committed first. And then the svn client
operations that expect to operate on repository revisions aren't
a real good fit.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 21 18:20:07 2006