From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa] signals 1/3 - move target_signal handling out of target.c
Date: Thu, 19 Jul 2001 11:09:00 -0000 [thread overview]
Message-ID: <20010719110921.A17652@nevyn.them.org> (raw)
In-Reply-To: <20010718110700.A1064@nevyn.them.org>
On Wed, Jul 18, 2001 at 11:07:00AM -0700, Daniel Jacobowitz wrote:
> I've also got a few small cleanups that can go in after the code moves (I
> want to keep them separate for revision history purposes). And I've got the
> necessary code to make gdbserver behave more-or-less correctly. Both of
> those will come along later, after this is approved. Nothing interesting
> here, just some 800 lines moved from one file to another.
No one yelled, so I committed this (with corrected ChangeLog).
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2001-07-19 11:09 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
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 [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=20010719110921.A17652@nevyn.them.org \
--to=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