From: Doug Evans <xdje42@gmail.com>
To: Gary Benson <gbenson@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v2] Separate out ANSI-standard signals
Date: Sun, 08 Jun 2014 00:55:00 -0000 [thread overview]
Message-ID: <CAP9bCMTR9e0WHRwjwYhbLWfBug=mA20AfOS4MLqhF8rMc42yhg@mail.gmail.com> (raw)
In-Reply-To: <20140606133230.GB1769@blade.nx>
On Fri, Jun 6, 2014 at 6:32 AM, Gary Benson <gbenson@redhat.com> wrote:
> Hi all,
>
> This patch reorders various pieces of code to separate ANSI-standard
> signals from other signals that need checking. Comments are added to
> document this.
>
> This patch differs from the first version in that extra comments have
> been added to document the ordering of the signals.
>
> Ok to commit?
>
> Cheers,
> Gary
>
> --
> gdb/
> 2014-06-06 Gary Benson <gbenson@redhat.com>
>
> * common/signals.c (gdb_signal_from_host): Reorder to separate
> the always-available ANSI-standard signals from the signals that
> require checking.
> (do_gdb_signal_to_host): Likewise.
> * proc-events.c (signal_table): Likewise.
>
> gdb/testsuite/
> 2014-06-06 Gary Benson <gbenson@redhat.com>
>
> * gdb.base/sigall.c [Functions to send signals]: Reorder to
> separate the always-available ANSI-standard signals from the
> signals that require checking.
> (main): Likewise.
> * gdb.reverse/sigall-reverse.c [Functions to send signals]:
> Likewise.
> (main): Likewise.
LGTM
next prev parent reply other threads:[~2014-06-08 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 13:32 Gary Benson
2014-06-08 0:55 ` Doug Evans [this message]
2014-06-09 9:36 ` [COMMITTED PATCH] " Gary Benson
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='CAP9bCMTR9e0WHRwjwYhbLWfBug=mA20AfOS4MLqhF8rMc42yhg@mail.gmail.com' \
--to=xdje42@gmail.com \
--cc=eliz@gnu.org \
--cc=gbenson@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).