Re: [PATCH 0/2] git-svn: fixes for intermittent SIGPIPE
- From
Roman Kagan <rkagan@mail.ru>
- Date
- Apr 23, 2012, 07:05 UTC
- Message-ID
- <CANiYKX5RNb3YXhGWXzpfDz+XK1PM6zyN=zrDKk3_4StCu2ukzg@mail.gmail.com>
- In-Reply-To
- <cover.1333381684.git.rkagan@mail.ru>
2 апреля 2012 г. 20:13 пользователь Roman Kagan <rkagan@mail.ru> написал:
Show 26 quoted lines
> 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(-)
IIUC the series was approved by Eric. What do I need to do now to have it reviewed for accepting into the master tree?
Thanks, Roman.