From: Florian Weimer <fweimer@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Linux: Implement per-thread user and group IDs
Date: Mon, 08 Jul 2019 10:42:00 -0000 [thread overview]
Message-ID: <87bly4x0x2.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <3a180167-70c4-1931-ac58-672c6a819528@redhat.com> (Carlos O'Donell's message of "Thu, 4 Jul 2019 00:06:38 -0400")
* Carlos O'Donell:
> This patch is OK for master if you cleanup the public comment you
> added in pthread.h to avoid the use of "flag" and instead only talk
> about scope.
Do you mean like this?
/* Change the property in *ATTR which indicates whether the thread has
its own current directory, file system root, and umask attribute.
SCOPE must be PTHREAD_PER_PROCESS_NP or PTHREAD_PER_THREAD_NP. By
default, new threads share these attributes with their creating
thread (PTHREAD_PER_PROCESS_NP). */
Thanks,
Florian
next prev parent reply other threads:[~2019-07-08 10:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 18:54 Florian Weimer
2019-06-28 19:06 ` Florian Weimer
2019-06-28 23:27 ` Carlos O'Donell
2019-06-30 9:36 ` Florian Weimer
2019-07-01 3:31 ` Carlos O'Donell
2019-07-01 4:50 ` Florian Weimer
2019-07-01 5:02 ` Carlos O'Donell
2019-07-01 16:35 ` Florian Weimer
2019-07-04 4:06 ` Carlos O'Donell
2019-07-08 10:42 ` Florian Weimer [this message]
2019-07-08 16:01 ` Carlos O'Donell
2019-07-04 21:38 ` Rich Felker
2019-07-08 8:26 ` Florian Weimer
2019-07-08 15:24 ` Rich Felker
2019-07-09 9:48 ` Florian Weimer
-- strict thread matches above, loose matches on Subject: below --
2018-12-13 13:02 Florian Weimer
2018-12-13 17:52 ` Joseph Myers
2018-12-13 18:09 ` Florian Weimer
2019-02-08 12:34 ` Florian Weimer
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=87bly4x0x2.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
/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).