From: Andrew Cagney <ac131313@redhat.com>
To: Jason Thorpe <thorpej@wasabisystems.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch rfc] Switch ns32k to CALL_DUMMY_BREAKPOINT_OFFSET
Date: Sat, 29 Mar 2003 22:14:00 -0000 [thread overview]
Message-ID: <3E861AA7.9040108@redhat.com> (raw)
In-Reply-To: <D331FFFB-6224-11D7-B839-000A957650EC@wasabisystems.com>
>
> On Saturday, March 29, 2003, at 10:51 AM, Andrew Cagney wrote:
>
> > Jason, got a machine to test this on? Or should this be assumed to work?
>
> I'd say go ahead and assume it's okay. I'm still in the process of putting together a PC532 (I finally got a SCSI->Ethernet adapter last week so I can hook it up to the network :-)
Ok, in it goes. No marks for anyone that guesses what the next patch is
....
thanks
Andrew
prev parent reply other threads:[~2003-03-29 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 18:52 Andrew Cagney
2003-03-29 20:24 ` Jason Thorpe
2003-03-29 22:14 ` Andrew Cagney [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=3E861AA7.9040108@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=thorpej@wasabisystems.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