From: Florian Weimer <fweimer@redhat.com>
To: Rical Jasan <ricaljasan@pacific.net>,
Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
"Carlos O'Donell" <carlos@redhat.com>
Subject: Re: [PATCH 3/3] manual: Add new header and standards annotations.
Date: Wed, 30 Nov 2016 10:45:00 -0000 [thread overview]
Message-ID: <c250e0e5-d019-f7bb-fa15-81f36ecd0424@redhat.com> (raw)
In-Reply-To: <951c0013-8227-46c3-6d05-678bca61f2ce@pacific.net>
On 11/30/2016 11:39 AM, Rical Jasan wrote:
> On 11/25/2016 06:53 AM, Joseph Myers wrote:
>> Where the function description would then have:
>>
>> Preliminary: | MT-Safe | AS-Safe | AC-Safe | *Note POSIX Safety
>> Concepts::.
>>
>> Standards: POSIX.1-2008 (unistd.h). *Note Feature Test Macros::.
>
> I like this. This is one of the avenues I was going to suggest, though
> I wasn't sure how amenable everybody would be to more boilerplate in
> *every single* description.
Many programmers would also find annotations which glibc version
introduced a particular functionality *extremely* useful, especially for
functions that were added after glibc 2.5 or so. It's not a standard as
such (but LSB would be), but I think it serves a similar purpose.
Can we reconsider adding this kind of information to the manual?
Thanks,
Florian
next prev parent reply other threads:[~2016-11-30 10:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 6:38 [PATCH 0/3] manual: Header & Standards Cleanup Rical Jasan
2016-11-23 6:38 ` [PATCH 2/3] manual: Convert @tables of variables to @vtables Rical Jasan
2016-11-23 6:38 ` [PATCH 1/3] manual: Refactor header and standards annotations Rical Jasan
2016-11-23 17:31 ` Joseph Myers
2016-11-24 9:34 ` Rical Jasan
2016-11-24 13:17 ` Joseph Myers
2016-11-25 3:44 ` Rical Jasan
2016-11-25 14:25 ` Joseph Myers
2016-11-30 8:58 ` Rical Jasan
2016-11-23 6:38 ` [PATCH 3/3] manual: Add new " Rical Jasan
2016-11-23 17:42 ` Joseph Myers
2016-11-24 10:22 ` Rical Jasan
2016-11-24 13:37 ` Joseph Myers
2016-11-25 5:59 ` Rical Jasan
2016-11-25 14:53 ` Joseph Myers
2016-11-25 15:09 ` Joseph Myers
2016-11-30 10:39 ` Rical Jasan
2016-11-30 10:45 ` Florian Weimer [this message]
2016-11-30 12:50 ` Joseph Myers
2016-12-02 11:54 ` Rical Jasan
2016-12-02 13:56 ` Joseph Myers
2016-12-05 7:59 ` Rical Jasan
2016-11-30 12:38 ` Joseph Myers
2016-12-05 5:33 ` Rical Jasan
2016-12-05 18:22 ` Joseph Myers
2016-12-06 10:57 ` Rical Jasan
2016-12-06 15:59 ` Joseph Myers
2016-12-06 16:36 ` Zack Weinberg
2016-11-25 7:36 ` Rical Jasan
2016-11-25 16:17 ` Joseph Myers
2016-11-30 10:46 ` Rical Jasan
2016-11-30 12:52 ` Joseph Myers
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=c250e0e5-d019-f7bb-fa15-81f36ecd0424@redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=mtk.manpages@gmail.com \
--cc=ricaljasan@pacific.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).