public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Rical Jasan <ricaljasan@pacific.net>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha <libc-alpha@sourceware.org>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Zack Weinberg <zackw@panix.com>,
	Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH v3] manual: Document missing feature test macros.
Date: Tue, 20 Feb 2018 08:30:00 -0000	[thread overview]
Message-ID: <b98bc081-0ae9-0465-949f-c1bdc81fa1d6@pacific.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1802191613100.32177@digraph.polyomino.org.uk>

On 02/19/2018 08:13 AM, Joseph Myers wrote:
> On Mon, 19 Feb 2018, Rical Jasan wrote:
> 
>> Several feature test macros are documented in features.h but absent in
>> the manual, and some documented macros accept undocumented values.
>> This commit updates the manual to mention all the accepted macros,
>> along with any values that hold special meaning.
>>
>> 	* manual/creature.texi (_POSIX_C_SOURCE): Document special
>> 	values of 199606L, 200112L, and 200809L.
>> 	(_XOPEN_SOURCE): Document special values of 600 and 700.
>> 	(_ISOC11_SOURCE): Document macro.
>> 	(_ATFILE_SOURCE): Likewise.
>> 	(_FORTIFY_SOURCE): Likewise.
> 
> OK.

Committed; 6a3962c4a408

Thanks,
Rical

      reply	other threads:[~2018-02-20  8:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28  3:49 [PATCH v2] " Rical Jasan
2017-08-10 11:57 ` [PING] " Rical Jasan
2017-08-10 22:27   ` Joseph Myers
2017-08-11  4:36     ` Rical Jasan
2017-08-11 11:31       ` Joseph Myers
2018-02-19 12:45 ` [PATCH v3] " Rical Jasan
2018-02-19 16:15   ` Joseph Myers
2018-02-20  8:30     ` Rical Jasan [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=b98bc081-0ae9-0465-949f-c1bdc81fa1d6@pacific.net \
    --to=ricaljasan@pacific.net \
    --cc=carlos@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=mtk.manpages@gmail.com \
    --cc=zackw@panix.com \
    /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).