From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Florian Weimer <fweimer@redhat.com>,
libc-alpha@sourceware.org, Zack Weinberg <zackw@panix.com>
Subject: Re: [PATCH v3][BZ 21340] add support for POSIX_SPAWN_SETSID
Date: Fri, 21 Apr 2017 20:43:00 -0000 [thread overview]
Message-ID: <c32aeac0-4a24-34b1-1f08-716cd5f4299c@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1704211952590.17579@digraph.polyomino.org.uk>
On 21/04/2017 16:53, Joseph Myers wrote:
> On Fri, 21 Apr 2017, Adhemerval Zanella wrote:
>
>> I think this iteration should fix the issues you bring.
>>
>> --
>>
>> Daurnimator <quae@daurnimator.com>
>> Adhemerval Zanella <adhemerval.zanella@linaro.org>
>>
>> [BZ #21340]
>> * posix/Makefile (tests): Add tst-posix_spawn-setsid to list of tests.
>> * posix/spawn.h: define POSIX_SPAWN_SETSID flag.
>> * posix/spawnattr_setflags.c (ALL_FLAGS): Add POSIX_SPAWN_SETSID to
>> valid flags.
>> * posix/tst-posix_spawn-setsid.c: Add test for POSIX_SPAWN_SETSID.
>> * sysdeps/mach/hurd/spawni.c (__spawni): Implementation of
>> POSIX_SPAWN_SETSID.
>> * sysdeps/posix/spawni.c (__spawni): Likewise.
>> * sysdeps/unix/sysv/linux/spawni.c (__spawni_child): Likewise.
>
> I think you should also add a NEWS entry for the new feature.
>
I will add one.
next prev parent reply other threads:[~2017-04-21 20:43 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 [this message]
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
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=c32aeac0-4a24-34b1-1f08-716cd5f4299c@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--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).