Whoops.
When I said update I meant commit.
Karl's pre-commit idea sounds good.
Sorry about the confusion.
gat
Ben Collins-Sussman wrote:
> "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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 8 04:38:31 2002