From: Stephen Kitt <steve@sk2.org>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: [3/3] Spelling fixes
Date: Thu, 02 Jun 2011 17:08:00 -0000 [thread overview]
Message-ID: <20110602170738.GM31021@sk2.org> (raw)
In-Reply-To: <4DE792B0.6000700@redhat.com>
Hi Nick,
On Thu, Jun 02, 2011 at 02:40:00PM +0100, Nick Clifton wrote:
> Thanks for reporting these problems.
You're welcome!
> I have checked in the attached patch in order to fix the spelling
> mistakes in the binutils sources. The only omissions are the .po
> files, which will wait for updated translations to be submitted, and
> the libiberty/pex-win32.c source file. The files in the libiberty
> directory are not part of the binutils project - they are their own
> project.
Thanks! I'll submit the pex-win32.c changes to the libiberty project
directly.
Regards,
Stephen
prev parent reply other threads:[~2011-06-02 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 7:35 [1/3] " Stephen Kitt
2011-05-26 7:37 ` [2/3] " Stephen Kitt
2011-05-26 7:38 ` [3/3] " Stephen Kitt
2011-06-02 13:39 ` Nick Clifton
2011-06-02 17:08 ` Stephen Kitt [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=20110602170738.GM31021@sk2.org \
--to=steve@sk2.org \
--cc=binutils@sourceware.org \
--cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).