From: Kyle McKay <mackyle@gmail.com>
To: git@vger.kernel.org
Cc: David Rothenberger <daveroth@acm.org>, Petr Baudis <pasky@ucw.cz>,
Jonathan Nieder <jrnieder@gmail.com>,
Daniel Shahaf <danielsh@apache.org>
Subject: [PATCH 0/2] allow git-svn fetching to work using serf
Date: Fri, 5 Jul 2013 20:41:58 -0700 [thread overview]
Message-ID: <CB53C901-3643-46AE-AA80-CED5E20AC3B7@gmail.com> (raw)
This patch allows git-svn to fetch successfully using the
serf library when given an https?: url to fetch from.
Unfortunately some svn servers do not seem to be configured
well for use with the serf library. This can cause fetching
to take longer compared to the neon library or actually
cause timeouts during the fetch. When timeouts occur
git-svn can be safely restarted to fetch more revisions.
A new temp_is_locked function has been added to Git.pm
to facilitate using the minimal number of temp files
possible when using serf.
The problem that occurs when running git-svn fetch using
the serf library is that the previously used temp file
is not always unlocked before the next temp file needs
to be used.
To work around this problem, a new temp name is used
if the temp name that would otherwise be chosen is
currently locked.
This patch may not be all that is required, but at least
it is a starting point.
Daniel Shahaf has suggested also setting "servers:global:http-bulk-
updates=on".
Kyle J. McKay (2):
Git.pm: add new temp_is_locked function
git-svn: allow git-svn fetching to work using serf
perl/Git.pm | 17 ++++++++++++++++-
perl/Git/SVN/Fetcher.pm | 6 ++++--
2 files changed, 20 insertions(+), 3 deletions(-)
--
1.8.3
next reply other threads:[~2013-07-06 3:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-06 3:41 Kyle McKay [this message]
2013-07-06 7:17 ` [PATCH 0/2] allow git-svn fetching to work using serf David Rothenberger
2013-07-07 0:28 ` Jonathan Nieder
2013-07-07 1:24 ` Kyle McKay
2013-07-07 1:37 ` Jonathan Nieder
2013-07-07 2:46 ` Kyle McKay
2013-07-07 17:40 ` Jonathan Nieder
2013-07-07 3:44 ` David Rothenberger
2013-07-07 17:53 ` Jonathan Nieder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CB53C901-3643-46AE-AA80-CED5E20AC3B7@gmail.com \
--to=mackyle@gmail.com \
--cc=danielsh@apache.org \
--cc=daveroth@acm.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=pasky@ucw.cz \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).