public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Dmitry V. Levin" <ldv@altlinux.org>, elfutils-devel@sourceware.org
Subject: Re: [PATCH 00/12] Fix spelling typos in comments, tests, and text files
Date: Sat, 12 Dec 2020 18:17:02 +0100	[thread overview]
Message-ID: <0ef61dc53e92682f215b44be9c1b48e4070bf5de.camel@klomp.org> (raw)
In-Reply-To: <20201212164901.GA474@altlinux.org>

Hi Dmitry,

On Sat, 2020-12-12 at 19:49 +0300, Dmitry V. Levin wrote:
> This is the least significant part of all spelling fixes, most users
> won't notice any difference at all, but it still makes sense to use
> correct spelling.
> 
> Dmitry V. Levin (12):
>   debuginfod: fix spelling typos in error diagnostics and comments
>   backends: fix spelling typos in comments
>   config: fix spelling typos in comments and %changelog
>   libasm: fix spelling typos in comments
>   libcpu: fix spelling typos in comments
>   libdw: fix spelling typos in comments and ChangeLog
>   libdwelf: fix spelling typos in comments
>   libdwfl: fix spelling typos in comments and ChangeLog
>   libelf: fix spelling typos in comments
>   src: fix spelling typos in comments and ChangeLog
>   tests: fix spelling typos in error diagnostics and comments
>   Fix spelling typos in NEWS, NOTES, TODO, and in comments of
>     configure.ac

Wow thanks. All changes look correct. I wouldn't have bothered with the
ChangeLog entry updates. But given you already did the work lets just
include them. All 12 patches pushed.

I saw you also fixed the spelling issues in elf.h. I'll sync it from
glibc again and add support for SHF_GNU_RETAIN.

Cheers,

Mark

      parent reply	other threads:[~2020-12-12 17:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-12 16:49 Dmitry V. Levin
2020-12-12 16:50 ` [PATCH 01/12] debuginfod: fix spelling typos in error diagnostics and comments Dmitry V. Levin
2020-12-12 16:50 ` [PATCH 02/12] backends: fix spelling typos in comments Dmitry V. Levin
2020-12-12 16:50 ` [PATCH 03/12] config: fix spelling typos in comments and %changelog Dmitry V. Levin
2020-12-12 16:50 ` [PATCH 04/12] libasm: fix spelling typos in comments Dmitry V. Levin
2020-12-12 16:50 ` [PATCH 05/12] libcpu: " Dmitry V. Levin
2020-12-12 16:51 ` [PATCH 06/12] libdw: fix spelling typos in comments and ChangeLog Dmitry V. Levin
2020-12-12 16:51 ` [PATCH 07/12] libdwelf: fix spelling typos in comments Dmitry V. Levin
2020-12-12 16:51 ` [PATCH 08/12] libdwfl: fix spelling typos in comments and ChangeLog Dmitry V. Levin
2020-12-12 16:52 ` [PATCH 09/12] libelf: fix spelling typos in comments Dmitry V. Levin
2020-12-12 16:52 ` [PATCH 10/12] src: fix spelling typos in comments and ChangeLog Dmitry V. Levin
2020-12-12 16:52 ` [PATCH 11/12] tests: fix spelling typos in error diagnostics and comments Dmitry V. Levin
2020-12-12 16:52 ` [PATCH 12/12] Fix spelling typos in NEWS, NOTES, TODO, and in comments of configure.ac Dmitry V. Levin
2020-12-12 17:17 ` Mark Wielaard [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=0ef61dc53e92682f215b44be9c1b48e4070bf5de.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=ldv@altlinux.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).