[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

mixed revision working copy -- rationale?

From: Bob Proulx <bob_at_proulx.com>
Date: 2005-05-17 17:38:11 CEST

Why doesn't an 'svn commit' also automatically 'svn update'?

After an 'svn commit' the working copy is now in a mixed revision
working copy state. Among other places this is documented in the


But what I cannot find any documentation on is *why* this behaves this
way. It has been a confusing point for many users. At the time of
the commit your working copy must be up to date with the repository
and so an update at that point would not be slow as it would not be
copying any significant data. At that instant it would seem to mostly
just be bookkeeping.

The commit your changes section of the book does not mention this
issue at all. (I think it should. I would submit a suggestion but I
don't understand it.)


If someone had an example of when making a commit without updating the
working copy is desireable that would be great.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 17 17:44:47 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.