Re: working copy corruption when network connection lost

On Wed, Jan 02, 2002 at 06:49:46PM -0600, Karl Fogel wrote:
> Philip Martin <philip@codematters.co.uk> writes:
>...
> > The best solution would be to have commit/rollback semantics on the
> > working copy, but I don't know if this is feasible. Does cvs suffer
> > from the same problem?
>
> I think the best solution is for Subversion not to get into these
> situations in the first place, though there is the "svn cleanup"
> command, and some kind of local rollback might be possible too (maybe
> extend the functionality of "svn revert"?).

Euh... we *do* have a commit/rollback semantic in the working copy. That is
what the whole "action log" thing is about. We attempt to queue up all the
operations in the log and then run it upon completion.

What we *don't* have is a macro-level commit/rollback of changes to updates
to the working copy. This is based on the presumption that it is okay for
some parts of the tree to be newer or older than others. We only require
consistent/proper metadata.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org