From: Reuben Thomas <rrt@sc3d.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] Fix occurrences of typo "alligned"
Date: Fri, 25 Mar 2022 09:19:06 +0000 [thread overview]
Message-ID: <CAOnWdohsm5ZTRoyeQPFn=pL8nh2BCkFsQJJp--Pi1OGa3Y5TZw@mail.gmail.com> (raw)
In-Reply-To: <2aaec9d1-aaf8-4992-9b43-89a9b64a08fc@suse.com>
On Fri, 25 Mar 2022 at 08:58, Jan Beulich <jbeulich@suse.com> wrote:
> On 24.03.2022 17:29, Reuben Thomas via Binutils wrote:
> > Patch attached.
>
> I don't think this needs a patch to individual lines, but a proper update
> of the translations; some other translations don't have this message at
> all. The original message in the source file was already corrected in
> de194d857576 ("Fix spelling typos."), and I'm sure Nick would have updated
> the .po files if such would have been required along with changing the
> original messages.
>
OK, thanks! Sorry for the noise.
--
https://rrt.sc3d.org
prev parent reply other threads:[~2022-03-25 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 16:29 Reuben Thomas
2022-03-25 8:57 ` Jan Beulich
2022-03-25 9:19 ` Reuben Thomas [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='CAOnWdohsm5ZTRoyeQPFn=pL8nh2BCkFsQJJp--Pi1OGa3Y5TZw@mail.gmail.com' \
--to=rrt@sc3d.org \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).