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

[PATCH 3/3] git-svn: drop redundant blocking of SIGPIPE

From
Roman Kagan <rkagan@mail.ru>
Date
Apr 23, 2012, 16:26 UTC
Message-ID
<4ffb0267b9afed911665265524247a15f4e04c39.1335250396.git.rkagan@mail.ru>
In-Reply-To
<cover.1335250396.git.rkagan@mail.ru>
Now that SIGPIPE is ignored there's no point blocking it.
Signed-off-by: Roman Kagan <rkagan@mail.ru>
---
 git-svn.perl |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/git-svn.perl b/git-svn.perl
index aa14564..f8e9ef0 100755
--- a/git-svn.perl
+++ b/git-svn.perl
@@ -4070,7 +4070,7 @@ sub rev_map_set {
 	if ($update_ref) {
 		$sigmask = POSIX::SigSet->new();
 		my $signew = POSIX::SigSet->new(SIGINT, SIGHUP, SIGTERM,
-			SIGALRM, SIGPIPE, SIGUSR1, SIGUSR2);
+			SIGALRM, SIGUSR1, SIGUSR2);
 		sigprocmask(SIG_BLOCK, $signew, $sigmask) or
 			croak "Can't block signals: $!";
 	}
-- 
1.7.7.6
Previous: Roman KaganNext: Eric Wong
Message 4 of 6 in “git-svn: fixes for intermittent SIGPIPE”
  1. 0/3 git-svn: fixes for intermittent SIGPIPERoman Kagan, Apr 24, 2012
  2. 1/3 git-svn: use POSIX::sigprocmask to block signalsRoman Kagan, Apr 2, 2012
  3. 2/3 git-svn: ignore SIGPIPERoman Kagan, Apr 2, 2012
  4. 3/3 git-svn: drop redundant blocking of SIGPIPERoman Kagan, Apr 23, 2012
  5. Eric WongApr 24, 2012
  6. Junio C HamanoApr 24, 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.