update optimization / WC auto-update

I don't know if this has already been discussed, but there's some
case I'd like to see optimized: when a user is working in some
directory and does a succession of commits from a single working
copy (without commits from other sources). I think this happens
quite frequently (at least for me) and it would be nice if
Subversion had some optimization related to that.

First, in some directory (a working copy or a subdirectory), if the
revision of all the objects is N and the user does a commit and if
this commit has revision N+1, then all the objects can "safely" be
automatically updated to revision N+1 (of course, such a feature
could be optional). The goal of such an automatical update is to
avoid a mixed-revision directory, which can be annoying (see the
various complaints about failures due to mixed-revision directories).

Such a feature could be realized with some 3rd-party script, but it
would be inefficient. In particular, I suppose that the automatical
update itself doesn't need a repository access since the only change
(the commit N+1) happened locally (some additional information may
be needed in the internal WC data to remember that).

-- 
Vincent Lefèvre <vincent_at_vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org