git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/2] allow git-svn fetching to work using serf

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jul 7, 2013, 17:40 UTC
Message-ID
<20130707174043.GA9975@google.com>
In-Reply-To
<FBCA37F9-4988-4773-8D8D-9CB041C35289@gmail.com>

(cc-ing subversion's users@ list for advice) Kyle McKay wrote:

> On Jul 6, 2013, at 18:37, Jonathan Nieder wrote:
>> Kyle McKay wrote:
>>> Begin forwarded message:
Show 7 quoted lines
>>>> [2] http://subversion.tigris.org/issues/show_bug.cgi?id=2932
>>
>> Ah, thanks for the context.
>>
>> It's still not clear to me how we know that ra_serf driving the editor
>> in a non depth-first manner is the problem here.  Has that explanation
>> been confirmed somehow?
[...]
Show 5 quoted lines
> Since ra_serf makes multiple connections to the server (hard-coded
> to 4 prior to svn 1.8, defaults to 4 in svn 1.8 but can be set to
> between 1 and 8) it makes sense there would be multiple active calls
> to apply_textdelta if processing is done as results are received on
> the multiple connections.

Ah, that's worrisome. Do I understand you correctly that to work with ra_serf in skelta mode, callers need to make their apply_textdelta callback thread-safe?

Or do you just mean that the traversal order is based on the order in which results are received? That would be fine, as long as after each apply_textdelta call, close_file is called before the next apply_textdelta.

Jonathan
Previous: Kyle McKayNext: David Rothenberger
Message 7 of 9 in “allow git-svn fetching to work using serf”
  1. 0/2 allow git-svn fetching to work using serfKyle McKay, Jul 6, 2013
  2. David RothenbergerJul 6, 2013
  3. Jonathan NiederJul 7, 2013
  4. Kyle McKayJul 7, 2013
  5. Jonathan NiederJul 7, 2013
  6. Kyle McKayJul 7, 2013
  7. Jonathan NiederJul 7, 2013
  8. David RothenbergerJul 7, 2013
  9. Jonathan NiederJul 7, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.