From: Joseph Myers <joseph@codesourcery.com>
To: daurnimator <quae@daurnimator.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH v3][BZ 21340] add support for POSIX_SPAWN_SETSID
Date: Wed, 05 Apr 2017 12:31:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1704051226540.2659@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20170405054116.9007-1-quae@daurnimator.com>
On Wed, 5 Apr 2017, daurnimator wrote:
> 2017-04-05 Daurnimator <quae@daurnimator.com>
>
> [BZ #21340]
> * conform/data/spawn.h-data: Add POSIX_SPAWN_SETSID flag.
You should never add a symbol to the conform/ expectations unless it is
actually defined by a released standard. In a case like this, of a symbol
intended to be added in a future version, it should not be in the conform/
data, and should be conditioned on __USE_GNU in the headers.
Note that http://austingroupbugs.net/view.php?id=1044 has the issue8 tag,
meaning it's for the next major revision of POSIX, not a bug fix for a TC
for the current revision.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-04-05 12:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 5:41 daurnimator
2017-04-05 8:34 ` Florian Weimer
2017-04-05 11:01 ` Daurnimator
2017-04-06 12:37 ` Florian Weimer
2017-04-06 13:22 ` Zack Weinberg
2017-04-06 13:23 ` Florian Weimer
2017-04-06 13:24 ` Zack Weinberg
2017-04-07 12:27 ` Daurnimator
2017-04-07 13:46 ` Zack Weinberg
2017-04-09 13:22 ` Daurnimator
2017-04-21 5:04 ` Daurnimator
2017-04-21 12:39 ` Adhemerval Zanella
2017-04-21 14:13 ` Adhemerval Zanella
2017-04-21 14:24 ` Florian Weimer
2017-04-21 18:29 ` Adhemerval Zanella
2017-04-21 19:53 ` Joseph Myers
2017-04-21 20:43 ` Adhemerval Zanella
2017-04-21 20:04 ` Florian Weimer
2017-04-21 20:43 ` Adhemerval Zanella
2017-04-21 20:47 ` Florian Weimer
2017-04-21 18:24 ` Joseph Myers
2017-04-21 18:26 ` Adhemerval Zanella
2017-04-05 12:31 ` Joseph Myers [this message]
2017-04-05 12:44 ` Joseph Myers
2017-04-05 12:58 ` Szabolcs Nagy
2017-04-05 15:02 ` 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=alpine.DEB.2.20.1704051226540.2659@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=quae@daurnimator.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).