From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] allow gdb to access altivec registers - OK to commit?
Date: Wed, 02 Nov 2005 20:44:00 -0000 [thread overview]
Message-ID: <20051102133355.6fdd0957@ironwood.lan> (raw)
In-Reply-To: <200510311356.44832.pgilliam@us.ibm.com>
On Mon, 31 Oct 2005 13:56:44 -0800
Paul Gilliam <pgilliam@us.ibm.com> wrote:
> OK to commit? (was the previous posting by Kevin an OK to commit?)
Yes, my previous posting was an okay to commit.
Kevin
prev parent reply other threads:[~2005-11-02 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 20:31 [PATCH] allow gdb to access altivec registers Paul Gilliam
2005-10-17 21:05 ` Mark Kettenis
2005-10-17 21:06 ` Daniel Jacobowitz
2005-10-21 22:46 ` Paul Gilliam
2005-10-27 9:46 ` Kevin Buettner
2005-10-31 22:51 ` [PATCH] allow gdb to access altivec registers - OK to commit? Paul Gilliam
2005-11-01 0:27 ` Andreas Schwab
2005-11-02 20:44 ` Kevin Buettner [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=20051102133355.6fdd0957@ironwood.lan \
--to=kevinb@redhat.com \
--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