From: Daniel Shahaf <danielsh@apache.org>
To: "Branko Čibej" <brane@wandisco.com>
Cc: wSubversion Development <dev@subversion.apache.org>, git@vger.kernel.org
Subject: Re: git-svn "Temp file with moniker 'svn_delta' already in use" and skelta mode
Date: Sat, 6 Jul 2013 02:04:07 +0000 [thread overview]
Message-ID: <20130706020407.GA26200@minotaur.apache.org> (raw)
In-Reply-To: <51D7660F.6070901@wandisco.com>
On Sat, Jul 06, 2013 at 02:34:23AM +0200, Branko Čibej wrote:
> http://subversion.apache.org/docs/release-notes/1.7.html#svnrdump
> In other words, this is a limitation of the Serf-based backend that has
> been around since Subversion 1.4. I'm aware that it isn't documented as
> well as it should be, but the bulk-mode workaround exists in part as a
> workaround for that, effectively disabling the more efficient HTTPv2
> protocol.
Is it possible to set "SVNAllowBulkUpdates Prefer" on a per-client basis?
That would require two things: (1) for git-svn to identify itself as such via
the User-Agent string, (2) for httpd to support making the SVNAllowBulkUpdates
directive conditional on a request header.
next prev parent reply other threads:[~2013-07-06 2:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <kr6uvc$p8a$1@ger.gmane.org>
[not found] ` <51D7072A.6080909@wandisco.com>
[not found] ` <kr75h0$qg5$1@ger.gmane.org>
[not found] ` <51D7362B.1040803@wandisco.com>
[not found] ` <kr7il5$n0p$1@ger.gmane.org>
2013-07-06 0:34 ` git-svn "Temp file with moniker 'svn_delta' already in use" and skelta mode Branko Čibej
2013-07-06 2:04 ` Daniel Shahaf [this message]
2013-07-06 2:15 ` Daniel Shahaf
2013-07-06 4:23 ` Branko Čibej
2013-07-06 7:30 ` Bert Huijben
2013-07-05 20:48 David Rothenberger
2013-07-05 22:58 ` Kyle McKay
2013-07-05 23:07 ` David Rothenberger
2013-07-06 1:01 ` Kyle McKay
2013-07-06 2:02 ` David Rothenberger
2013-07-05 23:14 ` David Rothenberger
2013-07-06 3:41 ` Kyle 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=20130706020407.GA26200@minotaur.apache.org \
--to=danielsh@apache.org \
--cc=brane@wandisco.com \
--cc=dev@subversion.apache.org \
--cc=git@vger.kernel.org \
/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).