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

Re: [PATCH] start_command: reset disposition of all signals in child

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 8, 2023, 17:38 UTC
Message-ID
<xmqq8r9gtviv.fsf@gitster.g>
In-Reply-To
<376d3ea0-a3eb-4b25-8bf2-ca40c4699e26@gmail.com>
Phillip Wood <phillip.wood123@gmail.com> writes:
Show 6 quoted lines
> Oh I should have looked more carefully at the existing uses. It looks
> like it is only my sequencer patch that does
>
> 	sigchain_push(SIGINT, SIG_IGN);
> 	sigchain_push(SIGQUIT, SIG_IGN);
> 	res = run_command(...);

Hmph, does it mean this patch would become unnecessary, once you fix the above sequence to follow the pattern "to spawn and then ignore"?

Previous: Phillip WoodNext: Phillip Wood
Message 6 of 9 in “start_command: reset disposition of all signals in child”
  1. start_command: reset disposition of all signals in childPhillip Wood via GitGitGadget, Sep 8, 2023
  2. Junio C HamanoSep 8, 2023
  3. Phillip WoodSep 8, 2023
  4. Junio C HamanoSep 8, 2023
  5. Phillip WoodSep 8, 2023
  6. Junio C HamanoSep 8, 2023
  7. Phillip WoodSep 11, 2023
  8. Junio C HamanoSep 11, 2023
  9. Eric WongSep 8, 2023

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.