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

Re: svn commit: r22496 - branches/multiple-moves/subversion/include

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2006-11-29 17:11:03 CET

On 11/29/06, hwright@tigris.org <hwright@tigris.org> wrote:
> Author: hwright
> Date: Tue Nov 28 18:39:01 2006
> New Revision: 22496
> Log:
> On the multiple moves branch:
> Documentation tweak.
> * subversion/include/svn_client.h
> (svn_client_copy_into, svn_client_move_into): Add a doc note regarding
> atomicity.

Triggered by Ed's reaction: we do have atomicity in our working copy:
you create a log file with commands, flush that to disc and have the
log runner execute it. That way, we ensure the working copy is in a
known state after completing log execution. If log execution fails
half way, it's restartable with 'svn cleanup'.

If you want a series of operations to be 'atomic', you should use logs
to ensure it. I think this is the typical case where log-use is
preferred to mainain working copy consistency.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 29 17:11:34 2006

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