From: Jim Blandy <jimb@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: carlton@kealia.com, ac131313@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: osabi: correct test for compatible handlers
Date: Thu, 23 Oct 2003 21:20:00 -0000 [thread overview]
Message-ID: <vt28ynbtzwc.fsf@zenia.home> (raw)
In-Reply-To: <200310231538.h9NFch0a000511@elgar.kettenis.dyndns.org>
Since the only concerns raised about this change are stylistic, and
the general sense seems to be that it's preferable as is, I've
committed this change. If people are very concerned about whether
can_run_code_for is a separate function or not, we can always discuss
that as a separate patch.
next prev parent reply other threads:[~2003-10-23 21:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 22:23 Jim Blandy
2003-10-22 19:09 ` Andrew Cagney
[not found] ` <vt23cdlvy21 dot fsf at zenia dot home>
[not found] ` <3F970598 dot 9020908 at redhat dot com>
2003-10-22 19:11 ` Daniel Jacobowitz
2003-10-22 19:33 ` Andrew Cagney
2003-10-22 20:04 ` Jim Blandy
2003-10-22 22:32 ` Andrew Cagney
2003-10-22 23:16 ` Jim Blandy
2003-10-22 23:28 ` David Carlton
2003-10-23 15:39 ` Mark Kettenis
2003-10-23 21:20 ` Jim Blandy [this message]
2003-10-23 1:29 ` Andrew Cagney
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=vt28ynbtzwc.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=ac131313@redhat.com \
--cc=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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