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

Re: revision numbering (was: Re: Multiple projects in one repository!)

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-05-08 03:42:22 CEST

"Glenn A. Thompson" <gthompson@cdr.net> writes:

> Hey:
>
> Is there slick way to force this to happen?
> i.e. hold up a commit while another update is started.

A commit creates a transaction tree, compares it to the Head revision
tree (looking for any out-of-dateness conflicts), then declares the
transaction to be the new Head revision.

An update creates a transaction tree, then compares it to some
revision tree, then tosses the transaction.

Therefore, an update can't possibly interfere with a commit. The only
thing that might "hold up" a commit is if two commit-transactions
both attempt to become the new Head revision at exactly the same
time. One will get there first, and the other will have to re-try.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 8 03:45:28 2002

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