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

SVN Update/Commit Concurrency

From: Daniel Becroft <Daniel.Becroft_at_supercorp.com.au>
Date: Thu, 10 Jan 2008 19:01:06 +1000

Hi all,
What is the method that SVN uses to control commits that happen during another user's update?
For example, in the following scenario:
1. [UserA] svn update (HEAD is 100).
2. [UserB] svn commit (HEAD is 101) - happens while UserA's update is happening
When UserA's update has completed, will the working copy revision number be 100, or 101? I'm guessing that the first thing that the 'svn update' would do is to get the HEAD revision and store that, so it becomes a 'svn update --revision 100' command?
I've attempted to replicate this situation without success - I can't seem to make UserA's update go long enough.
Daniel B.
Received on 2008-01-10 10:03:47 CET

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.