public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3 07/13] libc.7: ffix
Date: Fri, 6 Jan 2023 00:53:11 +0100	[thread overview]
Message-ID: <7aa64afd-86ea-fa04-9e97-98b60ff8b264@gmail.com> (raw)
In-Reply-To: <20230105225303.bpo7ot4zcsthw2gv@illithid>


[-- Attachment #1.1: Type: text/plain, Size: 2201 bytes --]

Hi Branden,

On 1/5/23 23:53, G. Branden Robinson wrote:
> * Set page topic in lowercase.
> * Use typographer's quotation marks instead of '"' for quotation.

Isn't it equivalent in running text?  '"' is simpler to type.

> * Hyperlink the text "GNU C Library" to its website.
> 
> Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com>

Cheers,

Alex

> ---
>   man7/libc.7 | 13 +++++++------
>   1 file changed, 7 insertions(+), 6 deletions(-)
> 
> diff --git a/man7/libc.7 b/man7/libc.7
> index 5deba0a8e..43ec0269f 100644
> --- a/man7/libc.7
> +++ b/man7/libc.7
> @@ -3,21 +3,22 @@
>   .\"
>   .\" SPDX-License-Identifier: Linux-man-pages-copyleft
>   .\"
> -.TH LIBC 7 (date) "Linux man-pages (unreleased)"
> +.TH libc 7 (date) "Linux man-pages (unreleased)"
>   .SH NAME
>   libc \- overview of standard C libraries on Linux
>   .SH DESCRIPTION
> -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
>   a library of standard functions that can be used by all C programs
>   (and sometimes by programs in other languages).
>   Because of some history
>   (see below),
> -use of the term "libc"
> +use of the term \(lqlibc\(rq
>   to refer to the standard C library is somewhat ambiguous on Linux.
>   .SS glibc
> -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
>   .UR http://www.gnu.org\:/software\:/libc/
> +GNU C Library
>   .UE ,
>   often referred to as
>   .IR glibc .
> @@ -50,7 +51,7 @@ there was for a while
>   a fork of glibc 1.x created by Linux developers who felt that glibc
>   development at the time was not sufficing for the needs of Linux.
>   Often,
> -this library was referred to (ambiguously) as just "libc".
> +this library was referred to (ambiguously) as just \(lqlibc\(rq.
>   Linux libc released major versions 2, 3, 4, and 5,
>   as well as many minor versions of those releases.
>   Linux libc4 was the last version to use the a.out binary format,

-- 
<http://www.alejandro-colomar.es/>

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

  reply	other threads:[~2023-01-05 23:53 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 [this message]
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

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=7aa64afd-86ea-fa04-9e97-98b60ff8b264@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@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