Ben Collins-Sussman <sussman@collab.net> writes:
> If your working copy is all at revision 4, and you commit one file
> which creates revision 5, then that file is now at revision 5. That's
> it. Your working copy is never changed unless you explicitly fold new
> changes into it by running 'svn up'.
Hmmm... let me clarify what I'm guessing might be the confusion here.
Say your working copy is all at revision 4, and you commit one file
which creates revision 10. (Other people have been committing.) So
now what should your working copy do? Obviously, your copy of the
freshly committed file comes from revision 10. But what about the
rest of your working copy?
It would actually be *wrong* to claim your working copy is at revision
10 overall. What if somebody added or deleted something somewhere in
revisions 5 thru 9? There's simply no way to know without asking the
server to update your working directory to rev 10. And as I said
earlier, we don't want commits to automatically cause updates.
Thus after every commit, you end up with a mixed-revision working
copy. Not a big deal really. Many people do that on purpose: they
want to lock a directory or file at a certain revision, or mix and
match different pieces of a tree by using 'svn up -r' or 'svn switch'.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 7 07:29:54 2002