From: Jim Blandy <jimb@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: PowerPC: Add special-purpose register number enum
Date: Wed, 14 Jul 2004 23:08:00 -0000 [thread overview]
Message-ID: <vt2oemiur7g.fsf@zenia.home> (raw)
In-Reply-To: <20040712171858.53dfb287@saguaro>
Kevin Buettner <kevinb@redhat.com> writes:
> This looks like a duplicate of:
>
> http://sources.redhat.com/ml/gdb-patches/2004-07/msg00127.html
>
> If I'm mistaken on this point and it's *not* a duplicate, please
> let me know.
No, it's a duplicate; I saw that the log entry was munged, but didn't
realize (or remember) that I had already posted the broken version.
(I just realized yesterday I'd been having mail reader troubles.)
> I see that the ChangeLog entries are formatted better in this version
> though - the other one had some commas missing. So... when you commit,
> please use the above ChangeLog entries.
Yep.
prev parent reply other threads:[~2004-07-14 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 22:43 Jim Blandy
2004-07-13 0:19 ` Kevin Buettner
2004-07-14 23:08 ` Jim Blandy [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=vt2oemiur7g.fsf@zenia.home \
--to=jimb@redhat.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