From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Always define all of TARGET_SIGNAL_*
Date: Sat, 16 Mar 2002 18:38:00 -0000 [thread overview]
Message-ID: <3C94017B.2070201@cygnus.com> (raw)
In-Reply-To: <20020316212737.A1589@nevyn.them.org>
> I'm thinking of the net effect pulling both this patch and the other
>> pending signal patch onto the 5.1 would have. (I'm not sure if you ment
>> this or that I was confusing this patch with the other pending patches :-)
>
>
> The only patch I'd particularly like in 5.2 (not 5.1 :)) is the one to
> make gdbserver use signals.h, which I was going to address after this
> one was done (just to reduce confusion, not because of any dependence).
> I personally believe that pulling the others, particularly this one,
> into 5.2 will do no more harm than pulling them into the trunk; every
> day we leave them there is just a greater chance they'll be used this
> way.
I'm certaionly ok with (re-)pulling include/gdb/signals.h and
include/gdbserver into the 5.2 branch - just as long as core GDB on the
branch doesn't get modified to use them. This is also why I think
sitting on this enum patch until 5.2 is released is best/easiest.
As for what you posted, yep ok. But after 5.2 :-) Perhaphs a bug
report so it isn't forgotten.
enjoy,
Andrew
next prev parent reply other threads:[~2002-03-17 2:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 19:11 Daniel Jacobowitz
2002-02-28 6:57 ` Andrew Cagney
2002-02-28 8:51 ` Daniel Jacobowitz
2002-02-28 9:17 ` Andrew Cagney
2002-02-28 9:44 ` Daniel Jacobowitz
2002-03-10 16:20 ` Daniel Jacobowitz
2002-03-11 18:33 ` Andrew Cagney
2002-03-11 18:49 ` Daniel Jacobowitz
2002-03-11 20:01 ` Andrew Cagney
2002-03-16 18:27 ` Daniel Jacobowitz
2002-03-16 18:38 ` Andrew Cagney [this message]
2002-05-09 15:22 ` 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=3C94017B.2070201@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--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