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

Autoversioning and transactions

From: Sergey A. Lipnevich <sergeyli_at_pisem.net>
Date: 2003-05-05 22:46:51 CEST

Hi All!

Is the following statement true?
Autoversioning doesn't really lock files. But, there's still a
transactional guarantee. Let's say I and someone else commit changes to
a file F withing a repository with autoversioning enabled. I use the svn
client to do a commit, "someone else" is using a PUT command from a
WebDAV client. If I'm first, my transaction starts first, and my changes
are applied in their entirety, then "someone else's changes take over
(if needed, my changes can still be recovered from the previous revision
of the file F). If "someone else" is first, I will not be able to
commit: my transaction will not start because the file F in my working
copy is not up to date anymore. I will have to update and commit. So, no
files are ever left in the inconsistent state.
I also assume that PUTting a file will not change any of its existing
Is this thinking correct?
Thanks a lot!


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 5 22:47:47 2003

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

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