public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Vincent Lefevre <vincent@vinc17.net>, linux-man@vger.kernel.org
Subject: Re: [PATCH] printf.3: Fix wording for the 0 flag with given precision
Date: Fri, 31 Mar 2023 21:35:19 +0200	[thread overview]
Message-ID: <756bf5f3-a368-be05-5177-b113abf5741e@gmail.com> (raw)
In-Reply-To: <20230331143332.3649621-1-vincent@vinc17.net>


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

Hi Vincent,

On 3/31/23 16:33, Vincent Lefevre wrote:
> When a precision is given, the 0 flag is ignored only for integer
> conversions, not for all numeric conversions.

I think I've seen some related discussion in some other list,
right?  Could you please link to it in the commit message?

Thanks,

Alex

> 
> Signed-off-by: Vincent Lefevre <vincent@vinc17.net>
> ---
>  man3/printf.3 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man3/printf.3 b/man3/printf.3
> index 790ebf4d8..b90a71293 100644
> --- a/man3/printf.3
> +++ b/man3/printf.3
> @@ -324,7 +324,7 @@ and
>  flags both appear, the
>  .B \&0
>  flag is ignored.
> -If a precision is given with a numeric conversion
> +If a precision is given with an integer conversion
>  .RB ( d ,
>  .BR i ,
>  .BR o ,

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

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

  reply	other threads:[~2023-03-31 19:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 14:33 [PATCH] printf.3: Fix wording for the 0 flag with given precision Vincent Lefevre
2023-03-31 19:35 ` Alejandro Colomar [this message]
2023-04-01  1:46   ` Vincent Lefevre
2023-04-01 14:21     ` Alejandro Colomar

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=756bf5f3-a368-be05-5177-b113abf5741e@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=vincent@vinc17.net \
    /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