kbrannen@gte.net writes:
> Now we're good only after the "up". Is this a real problem or do I
> misunderstand the process somewhere? I thought that as long as I was
> the only developer with only 1 working dir, I'd never really have to
> do an "update"; true or false? If false, why?
You need to read chapter 2 of the book, particularly the last section.
In particular, this is a matter of understanding how mixed working
copies work. (Mixed-revision working copies, by the way, is nothing
new. It's a concept from CVS that we like very much.)
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'.
(The only alternative to this behavior is for every commit to *cause*
an immediate update of your whole working copy. And that mixes two
concepts that we don't want to mix: changes should only be submitted
when you run commit, and changes should be received only when you run
update.)
---------------------------------------------------------------------
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:18:49 2002