Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Always define all of TARGET_SIGNAL_*
Date: Mon, 11 Mar 2002 18:49:00 -0000	[thread overview]
Message-ID: <20020311214925.C462@nevyn.them.org> (raw)
In-Reply-To: <3C8D68D8.8050403@cygnus.com>

On Mon, Mar 11, 2002 at 09:32:56PM -0500, Andrew Cagney wrote:
> 
> >Now that we've got a "gdb/signals.h", there's a place to fix this
> >properly in the trunk.  How does this patch look?
> 
> Can I suggest sitting on this until after 5.2 is out!  If the change is 
> put on hold, then it will be easier to refresh the branch gdbserver from 
> the trunk.
> 
> The addition of things like a src/include/gdb/ directory to the branch 
> shouldn't be an issue provided GDB proper doesn't try (get modified) to 
> use it.

I think you're thinking of my other pending signals patch?  This is the
one that has nothing to do with gdbserver, and I was just waiting for
the branch to be cut.  If you'd rather I just hold it a bit longer
that's fine by me, though.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-03-12  2:49 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 [this message]
2002-03-11 20:01             ` Andrew Cagney
2002-03-16 18:27               ` Daniel Jacobowitz
2002-03-16 18:38                 ` Andrew Cagney
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=20020311214925.C462@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@cygnus.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