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

Re: [PATCH 1/3] git-svn: use POSIX::sigprocmask to block signals

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 23, 2012, 21:13 UTC
Message-ID
<xmqqd36yi228.fsf@junio.mtv.corp.google.com>
In-Reply-To
<CANiYKX68AJyE3+3BT7QSjziGS=HGKuk95rxS_04c0sGz9pywXw@mail.gmail.com>
Roman Kagan <rkagan@mail.ru> writes:
> [B]locking some signals is obviously not a good enough
> protection measure: the program may die on SIGKILL or the power may go
> off.

Ahh, that is what you meant. I agree that it is of dubious value to only try to catch signals, even though it may be better than nothing.

It should be sufficient to replace the "[...]" part with the above, and conclude it with "But it will be a separate topic that this patch does not address." or something.

Thanks.
Previous: Roman KaganNext: Roman Kagan
Message 5 of 7 in “git-svn: fixes for intermittent SIGPIPE”
  1. 0/3 git-svn: fixes for intermittent SIGPIPERoman Kagan, Apr 23, 2012
  2. 1/3 git-svn: use POSIX::sigprocmask to block signalsRoman Kagan, Apr 2, 2012
  3. Junio C HamanoApr 23, 2012
  4. Roman KaganApr 23, 2012
  5. Junio C HamanoApr 23, 2012
  6. 2/3 git-svn: ignore SIGPIPERoman Kagan, Apr 2, 2012
  7. 3/3 git-svn: drop redundant blocking of SIGPIPERoman Kagan, Apr 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.