From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: drow@false.org (Daniel Jacobowitz)
Cc: carlos@baldric.uwo.ca, dave.anglin@nrc-cnrc.gc.ca,
gdb@sources.redhat.com
Subject: Re: gdb 6.0
Date: Mon, 01 Mar 2004 18:42:00 -0000 [thread overview]
Message-ID: <200403011842.i21IgqKa021349@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <20040301183629.GA5277@nevyn.them.org> from "Daniel Jacobowitz" at Mar 1, 2004 01:36:29 pm
> Yes, and HP/UX support in the current CVS source is pretty good; but
> the PA Linux patches will not apply without some serious work.
I have some cleanups for HP/UX which I can now submit as my gdb
paperwork is now complete. I did a build last night and a few new
warnings have appeared since early Jan.
Carlos had offered to work on getting the debian PA Linux patches
integrated.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next prev parent reply other threads:[~2004-03-01 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 18:11 John David Anglin
2004-03-01 18:14 ` Daniel Jacobowitz
2004-03-01 18:33 ` John David Anglin
2004-03-01 18:36 ` Daniel Jacobowitz
2004-03-01 18:42 ` John David Anglin [this message]
2004-03-01 20:14 ` Andrew Cagney
2004-03-01 20:16 ` 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=200403011842.i21IgqKa021349@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=carlos@baldric.uwo.ca \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=drow@false.org \
--cc=gdb@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