public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3 07/13] libc.7: ffix
Date: Sun, 8 Jan 2023 16:59:17 -0600	[thread overview]
Message-ID: <20230108225917.7pdcvrndo2rhhs2w@illithid> (raw)
In-Reply-To: <d5e09698-fe05-e33c-045d-2f10d0a6faf1@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 780 bytes --]

Hi Alex,

At 2023-01-07T00:40:50+0100, Alejandro Colomar wrote:
> I've already pushed the changes to kernel.org.  Please rebase and
> prepare v4 when you're ready.

Thanks!  Will do.

> > -The term "libc" is commonly used as a shorthand for
> > -the "standard C library",
> > +The term \(lqlibc\(rq is commonly used as a shorthand for
> > +the \(lqstandard C library\(rq
> 
> The comma was accidentally removed, right?

Whoops.  But it comes back in:

libc.7: Revise content
> 
> > -By far the most widely used C library on Linux is the GNU C Library
> > +By far the most widely used C library on Linux is the
> 
> I think this "by far" deserves a comma.

In a subsequent commit,

libc.7: wfix

I recast the phrase away entirely.

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-01-08 22:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 22:53 [PATCH v3 07/13] libc.7: ffix G. Branden Robinson
2023-01-05 23:53 ` Alejandro Colomar
2023-01-06  0:17   ` G. Branden Robinson
2023-01-06  0:39     ` Alejandro Colomar
2023-01-06  7:25       ` G. Branden Robinson
     [not found]       ` <20230106071642.ukwraci3kp5sa74r@illithid>
2023-01-06 12:06         ` Alejandro Colomar
2023-01-06  7:24     ` How Groupe Bull screwed French with ISO 8859-1 (was: [PATCH v3 07/13] libc.7: ffix) G. Branden Robinson
2023-01-06 23:40 ` [PATCH v3 07/13] libc.7: ffix Alejandro Colomar
2023-01-08 22:59   ` G. Branden Robinson [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=20230108225917.7pdcvrndo2rhhs2w@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.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