From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: dmj+@andrew.cmu.edu
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] signals 1/3 - move target_signal handling out of target.c
Date: Wed, 18 Jul 2001 13:42:00 -0000 [thread overview]
Message-ID: <9003-Wed18Jul2001230900+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <20010718110700.A1064@nevyn.them.org>
> Date: Wed, 18 Jul 2001 11:07:00 -0700
> From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
>
> * target.c (struct signals): Move to signals.c.
> * target.c (target_signal_to_name): Likewise.
> * target.c (target_signal_from_name): Likewise.
> * target.c (target_signal_from_host): Likewise.
> * target.c (do_target_signal_to_host): Likewise.
> * target.c (target_signal_to_host_p): Likewise.
> * target.c (target_signal_to_host): Likewise.
> * target.c (target_signal_from_command): Likewise.
This should be one entry, not half a dozen entries:
* target.c (struct signals, target_signal_to_name)
(target_signal_from_name, target_signal_from_host)
(do_target_signal_to_host, target_signal_to_host_p)
(target_signal_to_host, target_signal_from_command): Move to
signals.c.
> * target.c (initialize_targets): Move check of
> struct signals to...
And this should not state the file name, since it's the same as the
previous entries:
(initialize_targets): Move check of struct signals to...
The GNU coding standards have more details about formatting ChangeLog
entries.
next prev parent reply other threads:[~2001-07-18 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 11:07 Daniel Jacobowitz
2001-07-18 13:42 ` Eli Zaretskii [this message]
2001-07-18 14:43 ` Daniel Jacobowitz
[not found] ` <3B55FC9C.3080306@cygnus.com>
2001-07-18 14:47 ` Daniel Jacobowitz
2001-07-18 15:00 ` Andrew Cagney
2001-07-18 15:37 ` Daniel Jacobowitz
2001-07-19 11:09 ` Daniel Jacobowitz
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=9003-Wed18Jul2001230900+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=dmj+@andrew.cmu.edu \
--cc=gdb-patches@sources.redhat.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