public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Dr. Jürgen Sauermann" <mail@xn--jrgen-sauermann-zvb.de>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: [patch] for the printf.3 man page
Date: Tue, 19 Jul 2022 16:57:50 +0200	[thread overview]
Message-ID: <ff476100-d800-2673-5b76-2c50070d4c86@gmail.com> (raw)
In-Reply-To: <30e334f2-8134-40f4-f956-ae6f7c0b3fb9@xn--jrgen-sauermann-zvb.de>


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

Hi Jürgen,

On 7/7/22 11:33, Dr. Jürgen Sauermann wrote:
> Hi Alex,
> 
> yes, sorry. Here it is (attached and inline):

Patch applied.

Thanks,

Alex

> 
> 
> --- printf.3    2022-07-06 14:59:39.443234437 +0200
> +++ printf.3.new    2022-07-06 15:16:08.986946363 +0200
> @@ -378,6 +378,10 @@
>   cannot parse this option and will issue a warning.
>   (SUSv2 did not
>   include \fI%\(aqF\fP, but SUSv3 added it.)
> +Note also that the default locale of a C program is "C" whose locale 
> information
> +indicates no thousands' grouping character. Therefore, without a prior
> +.BR setlocale (3)
> +no thousands' grouping characters will be printed.
>   .PP
>   glibc 2.2 adds one further flag character.
>   .TP
> 
> 
> Jürgen
> 
> 
> On 7/7/22 1:14 AM, Alejandro Colomar wrote:
>> Hi Jürgen,
>>
>>
>> Please send your patch in diff -u format.  See
>> <https://www.kernel.org/doc/man-pages/patches.html>
>>
>> Thanks,
>>
>> Alex
>>
> 

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

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

      parent reply	other threads:[~2022-07-19 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 13:31 [patch] for the printf.3 man page Dr. Jürgen Sauermann
2022-07-06 23:14 ` Alejandro Colomar
     [not found]   ` <30e334f2-8134-40f4-f956-ae6f7c0b3fb9@xn--jrgen-sauermann-zvb.de>
2022-07-19 14:57     ` Alejandro Colomar [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=ff476100-d800-2673-5b76-2c50070d4c86@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mail@xn--jrgen-sauermann-zvb.de \
    /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