From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Krzysztof Mazur <krzysiek@podlesie.net>,
Paul Fox <pgf@foxharp.boston.ma.us>,
git@vger.kernel.org
Subject: Re: Topics currently in the Stalled category
Date: Wed, 21 Nov 2012 15:13:48 -0500 [thread overview]
Message-ID: <20121121201348.GG16280@sigill.intra.peff.net> (raw)
In-Reply-To: <7va9ua20nz.fsf@alter.siamese.dyndns.org>
On Wed, Nov 21, 2012 at 11:53:04AM -0800, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > [1] Given the core-dumping behavior of SIGQUIT, I suspect it is not
> > nearly as widely used as SIGINT, but it sounds more like the
> > principle of least surprise to treat them the same.
>
> Sounds sensible. I wonder what happens when the editor is suspended
> ;-)
I think we would want to leave SIGTSTP alone; the editor should
typically respect it, and we would want to also pause until we get
SIGCONT (although even if we did continue, we would just be blocking on
wait() for the editor, anyway, so it is not a big deal).
Implicit in my "least surprise" comment above is that handling SIGQUIT
would match what system(3) does, so it makes sense to me to match that
(it also blocks SIGCHLD, but I do not think that really matters from a
user-visible perspective).
-Peff
next prev parent reply other threads:[~2012-11-21 20:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 2:46 Topics currently in the Stalled category Paul Fox
2012-11-21 9:27 ` Krzysztof Mazur
2012-11-21 19:34 ` Jeff King
2012-11-21 19:50 ` Paul Fox
2012-11-21 19:53 ` Junio C Hamano
2012-11-21 20:13 ` Jeff King [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-19 23:55 What's cooking in git.git (Nov 2012, #06; Mon, 19) Junio C Hamano
2012-11-20 23:50 ` Junio C Hamano
2012-11-21 0:05 ` Topics currently in the Stalled category Junio C Hamano
2012-11-21 3:31 ` Felipe Contreras
2012-11-28 2:59 ` Jeff King
2012-11-28 3:10 ` Felipe Contreras
2012-11-28 3:12 ` Jeff King
2012-11-28 3:11 ` Jeff King
2012-11-28 3:15 ` Felipe Contreras
2012-11-28 3:22 ` Jeff King
2012-11-28 3:33 ` Felipe Contreras
2012-11-21 14:55 ` Marc Branchaud
2012-11-22 11:24 ` Nguyen Thai Ngoc Duy
2012-12-01 0:36 ` Adam Spiers
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121121201348.GG16280@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=krzysiek@podlesie.net \
--cc=pgf@foxharp.boston.ma.us \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).