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

Re: how does our commit-finalization race logic *really* work?

From: <kmradke_at_rockwellcollins.com>
Date: Wed, 11 Feb 2009 10:36:31 -0600

sussman_at_gmail.com wrote on 02/11/2009 10:24:53 AM:

> On Wed, Feb 11, 2009 at 10:08 AM, C. Michael Pilato
<cmpilato_at_collab.net> wrote:
> >
> > How, if at all, does the behavior differ if you do this over svnserve
> > ra-local?
> Both svn:// and file:// succeed perfectly. All 40 commits go through.
> Good call. So something is fubar in either ra_neon or mod_dav_svn...
> somehow our HTTP layer is being way more, erm, restrictive than
> libsvn_fs needs it to be. Should we investigate further?

If it matters, I've had numerous users complain about this
situation, since they have modified a completely unrelated
part of the tree, but still need to "update" before commit.
This can be a little painful on a heavily used repository.
I.E. you can't update and commit fast enough before someone
else has committed, so you need to just need to manually
continue to update/commit until it works...

Kevin R.

Received on 2009-02-11 17:36:50 CET

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.