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, 01:37 UTC
Message-ID
<20130707013747.GM30132@google.com>
In-Reply-To
<1D11122F-5C75-4FAC-80EA-D5DC65902403@gmail.com>
Kyle McKay wrote:
> On Jul 6, 2013, at 17:28, Jonathan Nieder wrote:
>> David Rothenberger wrote:
>>> On 7/5/2013 8:41 PM, Kyle McKay wrote:
Show 13 quoted lines
>>>> Daniel Shahaf has suggested also setting
>>>> "servers:global:http-bulk-updates=on".
>>>
>>> I have a patch that does this, but since turning on bulk updates has
>>> a possible performance penalty, I prefer your approach.
>>
>> I assume that's because http-bulk-updates defeats caching.  If so,
>> makes sense.
>>
>> Please forgive my ignorance: is there a bug filed about ra_serf's
>> misbehavior here?  Is it eventually going to be fixed and this is
>> just a workaround, or is the growth in temp file use something we'd
>> live with permanently?
[...]
>
> Begin forwarded message:
[...]
>> [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?

For example, does the workaround mentioned by danielsh work? Does using ra_neon instead of ra_serf avoid trouble as well? Is there a simple explanation of why violating the depth-first constraint would lead to multiple blob (i.e., file, not directory) deltas being opened in a row without an intervening close?

Jonathan
Previous: Kyle McKayNext: Kyle McKay
Message 5 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.