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

Re: SVN Update/Commit Concurrency

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: Thu, 10 Jan 2008 03:13:37 -0600

On Jan 10, 2008, at 03:01, Daniel Becroft wrote:

> 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.

You are correct. The working copy will contain whatever revision was
HEAD at the time the update began.

The exception is externals. If your project uses externals that do
not specify an explicit revision, then they will be updated to
whatever revision was HEAD at the time each external is updated.
Commits may have occurred between the time the update began and the
time the externals are each updated.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-10 10:14:38 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.