git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: "Kyle J. McKay" <mackyle@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
	David Rothenberger <daveroth@acm.org>,
	Eric Wong <normalperson@yhbt.net>
Subject: Re: [PATCH v4 2/2] git-svn: allow git-svn fetching to work using serf
Date: Thu, 18 Jul 2013 12:29:43 -0700	[thread overview]
Message-ID: <20130718192943.GT14690@google.com> (raw)
In-Reply-To: <ac83ba2812aee248275a0760bb39a00@f74d39fa044aa309eaea14b9f57fe79>

(cc-ing Eric Wong, who maintains git-svn and knows both it and
the libsvn perl bindings much better than I do)
Kyle J. McKay wrote:

> David Rothenberger <daveroth@acm.org> has determined the cause to
> be that ra_serf does not drive the delta editor in a depth-first
> manner [...]. Instead, the calls come in this order:

Thanks.

Sorry to nitpick, but the problem is not depth-first versus
breadth-first versus random.  Blaming the traversal order makes this
completely confusing.  The actual problem is that the driver asks us
to keep multiple files open at a time.

The approach taken in this patch would be racy if the driver calls us
multiple times concurrently (since temp_acquire can fail).  I believe
it doesn't but haven't checked.

The approach is generally good.  I wanted to propose some clearer
documentation for temp_is_locked() but didn't end up finding a moment
for it, so... meh.  I'll be happy to help get the details right if
someone else finds time for that (hint, hint).

Hope that helps,
Jonathan

  reply	other threads:[~2013-07-18 19:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18 19:15 [PATCH v4 0/2] allow git-svn fetching to work using serf Kyle J. McKay
2013-07-18 19:15 ` [PATCH v4 1/2] Git.pm: add new temp_is_locked function Kyle J. McKay
2013-07-18 19:15 ` [PATCH v4 2/2] git-svn: allow git-svn fetching to work using serf Kyle J. McKay
2013-07-18 19:29   ` Jonathan Nieder [this message]
2013-07-18 23:31     ` Kyle J. McKay
2013-07-18 23:40     ` Eric Wong
2013-07-18 23:34 ` [PATCH v4 0/2] " Junio C Hamano
2013-07-19  0:16   ` Kyle J. McKay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130718192943.GT14690@google.com \
    --to=jrnieder@gmail.com \
    --cc=daveroth@acm.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mackyle@gmail.com \
    --cc=normalperson@yhbt.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).