From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2023, #04; Tue, 12)
Date: Tue, 12 Sep 2023 12:34:16 -0700 [thread overview]
Message-ID: <xmqqy1hbmbif.fsf@gitster.g> (raw)
In-Reply-To: <12c956ea-330d-4441-937f-7885ab519e26@gmail.com> (Phillip Wood's message of "Tue, 12 Sep 2023 19:30:41 +0100")
Phillip Wood <phillip.wood123@gmail.com> writes:
> On 12/09/2023 17:57, Junio C Hamano wrote:
>> * pw/rebase-sigint (2023-09-07) 1 commit
>> - rebase -i: ignore signals when forking subprocesses
>> If the commit log editor or other external programs (spawned via
>> "exec" insn in the todo list) receive internactive signal during
>> "git rebase -i", it caused not just the spawned program but the
>> "Git" process that spawned them, which is often not what the end
>> user intended. "git" learned to ignore SIGINT and SIGQUIT while
>> waiting for these subprocesses.
>> Will merge to 'next'?
>> source: <pull.1581.git.1694080982621.gitgitgadget@gmail.com>
>
> This needs a re-roll to stop it ignoring signals in the child
> c.f. <376d3ea0-a3eb-4b25-8bf2-ca40c4699e26@gmail.com>
Yeah, you're right.
Thanks.
next prev parent reply other threads:[~2023-09-12 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 16:57 What's cooking in git.git (Sep 2023, #04; Tue, 12) Junio C Hamano
2023-09-12 17:32 ` Philippe Blain
2023-09-12 19:25 ` Junio C Hamano
2023-09-12 21:13 ` Philippe Blain
2023-09-12 18:30 ` Phillip Wood
2023-09-12 19:34 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-12 17:07 Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqy1hbmbif.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood123@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).