From: "Branko Čibej" <brane@wandisco.com>
To: users@subversion.apache.org
Cc: git@vger.kernel.org
Subject: Re: git-svn "Temp file with moniker 'svn_delta' already in use" and skelta mode
Date: Sat, 06 Jul 2013 06:23:57 +0200 [thread overview]
Message-ID: <51D79BDD.5020106@wandisco.com> (raw)
In-Reply-To: <51D7660F.6070901@wandisco.com>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
On 06.07.2013 02:34, Branko Čibej wrote:
> In the meantime, it might be a good idea to relax the restrictions in
> git-svn to account for the way the HTTPv2 protocol works.
By the way, this section of the 1.8 release notes is relevant:
http://subversion.apache.org/docs/release-notes/1.8.html#neon-deleted
In 1.8 there is a client-side configuration option called
http-bulk-updates that controls how the client will request data from
the server. It can be set in the ~/.subversion/servers file, or on the
comand-line by the option
--config-option=servers:global:http-bulk-updates=on
or, of course, in the client API context. git-svn should probably do the
latter as a simple workaround.
-- Brane
--
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane@wandisco.com
[-- Attachment #2: Type: text/html, Size: 1845 bytes --]
next prev parent reply other threads:[~2013-07-06 4:24 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
2013-07-06 2:15 ` Daniel Shahaf
2013-07-06 4:23 ` Branko Čibej [this message]
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=51D79BDD.5020106@wandisco.com \
--to=brane@wandisco.com \
--cc=git@vger.kernel.org \
--cc=users@subversion.apache.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.