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>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] printf.3: Fix wording for the 0 flag with given precision
Date: Sat, 1 Apr 2023 16:21:58 +0200	[thread overview]
Message-ID: <a2a5fa2c-cc79-9d35-9fd7-0bdc54b4c82f@gmail.com> (raw)
In-Reply-To: <20230401014604.GC7123@zira.vinc17.org>


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

Hi,

On 4/1/23 03:46, Vincent Lefevre wrote:
> Hi,
> 
> On 2023-03-31 21:35:19 +0200, Alejandro Colomar wrote:
>> 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?
> 
> If you mean my message "printf: 0 flag and given precision for %b" in
> the libc-alpha list, then this does not concern the printf man page
> yet, because this man page currently does not mention %b at all (%b
> is rather new, and not in the current C standard). This should be
> added to the man page, but this is not trivial, and I think that the
> inconsistency I've mentioned should be resolve in one way or the
> other before %b is added to the man page (in order to make sure that
> it does not contain something that could become obsolete).
> 
> So, does one really need the link in the commit message, while %b is
> not in the man page yet?

Nah, I thought it might have something to do with it.

I applied the patch.  Thanks,

Alex

> 

-- 
<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-04-01 14:22 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
2023-04-01  1:46   ` Vincent Lefevre
2023-04-01 14:21     ` 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=a2a5fa2c-cc79-9d35-9fd7-0bdc54b4c82f@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