From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <kettenis@gnu.org>
Cc: joseph@codesourcery.com, gdb-patches@sources.redhat.com
Subject: Re: [COMMIT] Prepare Solaris x86 for 64-bit Solaris 10
Date: Sun, 31 Oct 2004 15:58:00 -0000 [thread overview]
Message-ID: <41850B86.5060306@gnu.org> (raw)
In-Reply-To: <200410311535.i9VFZCxv001928@elgar.sibelius.xs4all.nl>
Mark Kettenis wrote:
> Date: Sat, 30 Oct 2004 16:59:28 -0400
> From: Andrew Cagney <cagney@gnu.org>
>
> What we're not going to add is screwed up #include inheritance, can you
> revert that?
>
> Damn. I'd hoped I could get away with that. Well, here's a different
> approach. Spreads the logic over two files so it becomes a bit more
> difficult to keep things in synch.
What ever.
I'd recommend the strategy I took for inf-ptrace, cut your losses and
start again. Create inf-procfs and from there inf-svr4 and finally the
solaris stuff you need.
Andrew
next prev parent reply other threads:[~2004-10-31 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-30 19:51 Mark Kettenis
2004-10-30 19:59 ` Joseph S. Myers
2004-10-30 20:53 ` Andrew Cagney
2004-10-30 21:13 ` Mark Kettenis
2004-10-30 21:59 ` Andrew Cagney
2004-10-31 15:35 ` Mark Kettenis
2004-10-31 15:58 ` Andrew Cagney [this message]
2004-10-31 21:24 ` Joseph S. Myers
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=41850B86.5060306@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=joseph@codesourcery.com \
--cc=kettenis@gnu.org \
/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