[meant to post this to the list]
2008/9/13 Lira Olavo <Olavo.LIRA_at_gemalto.com>:
> Yes but isn't it the same as working within a team? It is like you
> commit something and then someone after you commit a new version, so
> your version now is not up-to-date. Why would you call it "break the
> checkout"?
The difference is probably when you do an update the client doesn't
know something has changed in the revision it committed and so doesn't
download that change? I'm guessing here as I'm new to subversion and
trying to learn it all fast :)
In my case one of the reasons I may want to do this is to pin an
svn:externals property on making a Tag. I figure in this case that
it's ok as the client isn't going to switch to that tag, it just wants
to create it, so we pin the externals to the current latest revision
and then the Tag is truly fixed (esp. as the pre-commit hook won't
allow further changes to it - or at least it won't when I write it
hopefully!)
Thanks for the answer :)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-13 22:45:13 CEST