From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] undefine SIGHUP if function kill not available...
Date: Thu, 08 Jan 2009 15:30:00 -0000 [thread overview]
Message-ID: <20090108153039.GA7097@caradoc.them.org> (raw)
In-Reply-To: <20090108135131.GF20220@adacore.com>
On Thu, Jan 08, 2009 at 05:51:31PM +0400, Joel Brobecker wrote:
> In any case, it looks relatively straightforward, but I'd rather
> have the confirmation from someone who's experienced with signals.
Looks fine to me.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-01-08 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 11:58 Joel Brobecker
2009-01-08 13:51 ` Joel Brobecker
2009-01-08 15:30 ` Daniel Jacobowitz [this message]
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=20090108153039.GA7097@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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