From: Nick Duffek <nsd@redhat.com>
To: dje@watson.ibm.com
Cc: china@thewrittenword.com, gdb-patches@sources.redhat.com,
kevinb@redhat.com
Subject: Re: [PATCH] bfd/rs6000-core.c
Date: Tue, 26 Jun 2001 07:33:00 -0000 [thread overview]
Message-ID: <200106251820.f5PIKY225156@rtl.cygnus.com> (raw)
In-Reply-To: <200106240523.BAA24138@makai.watson.ibm.com>
On 24-Jun-2001, David Edelsohn wrote:
> * rs6000-core.c: Use autoconf variable HAVE_ST_C_IMPL to guard use
> of c_impl field.
> * configure.in: Auto-configure HAVE_ST_C_IMPL.
> * configure.in: Likewise.
The patch looks good to me. Approved, unless Kevin has any objections.
I suggest also getting the binutils mailing list to rubber-stamp it before
committing it. There was talk about officially giving GDB ownership of
GDB-only files in bfd, but I don't think that's happened.
Nick
next prev parent reply other threads:[~2001-06-26 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-23 22:23 David Edelsohn
2001-06-26 7:33 ` Nick Duffek [this message]
2001-06-26 9:21 ` Kevin Buettner
2001-06-26 9:39 ` David Edelsohn
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=200106251820.f5PIKY225156@rtl.cygnus.com \
--to=nsd@redhat.com \
--cc=china@thewrittenword.com \
--cc=dje@watson.ibm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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