public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alex Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org,
	Walter Harms <wharms@bfs.de>
Subject: Re: [PATCH] register_printf_speficier.3, register_printf_modifier.3, register_printf_type.3: Add new manual page and links
Date: Mon, 19 Sep 2022 01:25:42 +0200	[thread overview]
Message-ID: <32dd590f-4f1c-c383-e195-d90fe6465385@gmail.com> (raw)
In-Reply-To: <20220918231812.htiqn5b77reriljg@illithid>


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

Hi Branden!

On 9/19/22 01:18, G. Branden Robinson wrote:
> At 2022-09-19T00:16:41+0200, Alex Colomar wrote:
>> I wrote this manual page after on an old discussion with Walter,
>> which I postponed too much.  I had a long time ago written some
>> using register_printf_specifier(3), and I remember having a lot of
>> trouble using, since there's few documentation about it, if at
>> all.  I had to guess much of it.
>> Well, please review this page, and comment anything you don't like.
> [...]
>>   man3/register_printf_speficier.3 | 439 +++++++++++++++++++++++++++++++
> 
> Well, for a start, I'd spell the new file name correctly, avoiding a
> controversial git rename in the future.  ;-)

Yeah, that may be a good start :)

I'm still far from pushing anything like that, so expect a lot of typos. 
  How about the layout and contents of the page?  Do you like them? 
Also I considered adding documentation about the related types in the 
same page, since this is one of those where the header is really small, 
and the types don't leak out of them, so we can have a true manual page 
(even if somewhat big, since those functions are a hell to understand, 
and therefore document).

Cheers,

Alex

> 
> Regards,
> Branden

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


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

  reply	other threads:[~2022-09-18 23:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-18 22:16 Alex Colomar
2022-09-18 22:36 ` Alex Colomar
2022-09-18 22:38   ` Alex Colomar
2022-09-18 23:09 ` [RFC v2] " Alex Colomar
2022-09-19  8:55   ` Alex Colomar
2022-09-18 23:18 ` [PATCH] " G. Branden Robinson
2022-09-18 23:25   ` Alex Colomar [this message]
2022-09-19 16:54 ` [RFC v3] printf.3head: Document functions for customizing printf(3)-like functions Alex Colomar
2022-09-19 16:54 ` [RFC v3 2/4] register_printf_specifier.3, register_printf_modifier.3, register_printf_type.3: Add links to printf.h(3head) Alex Colomar
2022-09-19 16:54 ` [RFC v3 3/4] printf_arginfo_size_function.3type, printf_function.3type, printf_info.3type, printf_va_arg_function.3type: " Alex Colomar
2022-09-19 16:54 ` [RFC v3 4/4] PA_CHAR.3const, PA_DOUBLE.3const, PA_FLAG_LONG.3const, PA_FLAG_LONG_DOUBLE.3const, PA_FLAG_LONG_LONG.3const, PA_FLAG_PTR.3const, PA_FLAG_SHORT.3const, PA_FLOAT.3const, PA_INT.3const, PA_LAST.3const, PA_POINTER.3const, PA_STRING.3const, PA_WCHAR.3const, PA_WSTRING.3const: " Alex 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=32dd590f-4f1c-c383-e195-d90fe6465385@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=wharms@bfs.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).