From: Roman Kagan <rkagan@mail.ru>
To: git@vger.kernel.org
Subject: [PATCH 0/2] git-svn: fixes for intermittent SIGPIPE
Date: Mon, 2 Apr 2012 20:13:36 +0400 (MSK) [thread overview]
Message-ID: <cover.1333381684.git.rkagan@mail.ru> (raw)
In my work environment subversion is still being used as the main
revision control system. Therefore many people who prefer to work with
git have to resort to git-svn.
However, in many configurations it used to suffer from the notorious
"git-svn died of signal 13" problem (see e.g.
http://thread.gmane.org/gmane.comp.version-control.git/134936 and the
links therein).
I believe to have tracked down the issue to the connection being closed
by the server when http keep-alive is in use, and the client dying on
SIGPIPE because its handler is left at SIG_DFL when a new request is
being made.
The patches have been tested on
- Linux Fedora 16 x86_64, git 1.7.7.6, perl v5.14.2, svn 1.6.17
- Windows 7 x64 + Cygwin, git 1.7.9, perl v5.10.1, svn 1.7.4,
- Windows 7 x64 + MsysGit, git 1.7.9.msysgit.0, perl v5.8.8, svn 1.4.6
Roman Kagan (2):
git-svn: use POSIX::sigprocmask to block signals
git-svn: ignore SIGPIPE
git-svn.perl | 20 ++++++++++++++------
1 files changed, 14 insertions(+), 6 deletions(-)
--
1.7.7.6
next reply other threads:[~2012-04-02 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 16:13 Roman Kagan [this message]
2012-04-02 16:13 ` [PATCH 1/2] git-svn: use POSIX::sigprocmask to block signals Roman Kagan
2012-04-10 21:11 ` Eric Wong
2012-04-11 11:22 ` Roman Kagan
2012-04-02 16:13 ` [PATCH 2/2] git-svn: ignore SIGPIPE Roman Kagan
2012-04-23 7:05 ` [PATCH 0/2] git-svn: fixes for intermittent SIGPIPE Roman Kagan
2012-04-23 14:44 ` Junio C Hamano
2012-04-23 15:10 ` Roman Kagan
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=cover.1333381684.git.rkagan@mail.ru \
--to=rkagan@mail.ru \
--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).