git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/2] git-svn: fixes for intermittent SIGPIPE

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 23, 2012, 14:44 UTC
Message-ID
<xmqqvckqld7q.fsf@junio.mtv.corp.google.com>
In-Reply-To
<CANiYKX5RNb3YXhGWXzpfDz+XK1PM6zyN=zrDKk3_4StCu2ukzg@mail.gmail.com>
Roman Kagan <rkagan@mail.ru> writes:
> IIUC the series was approved by Eric.  What do I need to do now to
> have it reviewed for accepting into the master tree?
I see this:
        Date: Tue, 10 Apr 2012 21:11:20 +0000
        From: Eric Wong <normalperson@yhbt.net>
        Message-ID: <20120410211120.GA27555@dcvr.yhbt.net>
        Roman Kagan <rkagan@mail.ru> wrote:
        > +		my $signew = POSIX::SigSet->new(SIGINT, SIGHUP, SIGTERM,
        > +			SIGALRM, SIGPIPE, SIGUSR1, SIGUSR2);
        Considering your 2/2 patch, can we remove SIGPIPE here?
        Otherwise, I think this series is good.  Thanks!

What usually happens after such an intial round of review is for you to think about the comments like this one given during the review, and either submit a patch updated accordingly, or discuss why your original is better than the suggested update, and then the reviewer responds to it, and repeat the process until everybody involved in the discussion accepts the outcome.

Then the patch will hit my 'next' branch (or my 'master' branch, for subsystems like git-svn where the area expert, i.e. Eric in this case, knows much better than myself) after that.

In short, as far as I can see, the ball is still in your court.
Thanks for a reminder, though.
Previous: Roman KaganNext: Roman Kagan
Message 7 of 8 in “git-svn: fixes for intermittent SIGPIPE”
  1. 0/2 git-svn: fixes for intermittent SIGPIPERoman Kagan, Apr 2, 2012
  2. 1/2 git-svn: use POSIX::sigprocmask to block signalsRoman Kagan, Apr 2, 2012
  3. Eric WongApr 10, 2012
  4. Roman KaganApr 11, 2012
  5. 2/2 git-svn: ignore SIGPIPERoman Kagan, Apr 2, 2012
  6. Roman KaganApr 23, 2012
  7. Junio C HamanoApr 23, 2012
  8. Roman KaganApr 23, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.