From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Fix misspellings in elf/ -- BZ 25337
Date: Mon, 29 May 2023 16:20:28 -0700 [thread overview]
Message-ID: <CALoOobOBUKfKNHMD6CDuEJpdMe2ipNStnmDPdyJHe4Kzf2VE7A@mail.gmail.com> (raw)
In-Reply-To: <3b37d4e2-6264-9950-1bf1-e468b8d348d7@redhat.com>
Carlos,
On Mon, May 29, 2023 at 2:44 PM Carlos O'Donell <carlos@redhat.com> wrote:
> Please note that correcting spellings is acceptable as a consensus commit:
> https://sourceware.org/glibc/wiki/Consensus#Consensus_topics
I asked here: https://sourceware.org/pipermail/libc-alpha/2023-May/148060.html,
and have been breaking up this (large) patch:
https://sourceware.org/pipermail/libc-alpha/2023-May/148355.html into
easier to review batches.
The remaining part is still pretty large:
359 files changed, 527 insertions(+), 527 deletions(-)
I can commit it as a single patch, or break it up into a few more
(sysdeps at 153 files changed, 214 insertions(+), 214 deletions(-) is
the largest remaining top-level directory).
Thanks!
--
Paul Pluzhnikov
prev parent reply other threads:[~2023-05-29 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 21:08 Paul Pluzhnikov
2023-05-29 21:44 ` Carlos O'Donell
2023-05-29 23:20 ` Paul Pluzhnikov [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=CALoOobOBUKfKNHMD6CDuEJpdMe2ipNStnmDPdyJHe4Kzf2VE7A@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
/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).