From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfc] dummy calls for hppa64-hpux
Date: Fri, 10 Dec 2004 21:35:00 -0000 [thread overview]
Message-ID: <20041210204708.GA17127@nevyn.them.org> (raw)
In-Reply-To: <20041210180102.GX29171@tausq.org>
On Fri, Dec 10, 2004 at 10:01:02AM -0800, Randolph Chung wrote:
> In reference to a message from Randolph Chung, dated Dec 08:
> > this patch is not yet ready for inclusion, i'm only posting it for
> > comments because it's rather unorthodox.
>
> ok, here's another unfinished idea..... Dave Anglin suggested an
> alternative scheme to me that seems more robust. I haven't written the
> code for it yet, but here's a 50-line comment to explain it. Comments
> before i try it? :)
I think this looks a whole lot better. If the space you're in can't
make inter-space calls, you probably won't need to do this anyway, so
issuing an error message is fine.
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-12-10 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 13:31 Randolph Chung
2004-12-10 19:04 ` Randolph Chung
2004-12-10 21:35 ` 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=20041210204708.GA17127@nevyn.them.org \
--to=drow@false.org \
--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