From: Ulrich Drepper <drepper@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: jeremy@goop.org, mingo@redhat.com, roland@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use group_leader->pgrp (was Re: setpgid and threads)
Date: Mon, 08 Sep 2003 21:38:30 -0700 [thread overview]
Message-ID: <3F5D5946.1030002@redhat.com> (raw)
In-Reply-To: <20030908211746.25fff0f1.akpm@osdl.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andrew Morton wrote:
> OK. There were a few missing ones. Here's what I have, against test5. Do
> you have a test suite which would give us reasonable confidence?
Nope, I don't.
Why not leave the element renamed for a test release or two. So the
nice people who do compile checks on all the drivers will find the
missing changes.
> Should setpgrp() in a thread affect the group leader? It does...
Yes. This the existence of a thread group leader different from current
means using the POSIX thread "process" semantics this is the case. All
the thread together have only one "process group" ("process" again in
the POSIX sense).
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/XVlG2ijCOnn/RHQRAnZnAJ0SaF7LUcbY/8XKxBnwYzW5pmpeYACglnWh
55qtBiGdqNyl6sAwR6OCPXg=
=5oJh
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-09-09 4:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1061424262.24785.29.camel@localhost.localdomain>
[not found] ` <20030820194940.6b949d9d.akpm@osdl.org>
2003-09-09 1:59 ` [PATCH] use group_leader->pgrp (was Re: setpgid and threads) Jeremy Fitzhardinge
2003-09-09 2:12 ` Andrew Morton
2003-09-09 2:13 ` Jeremy Fitzhardinge
2003-09-09 3:21 ` Andrew Morton
2003-09-09 3:54 ` Ulrich Drepper
2003-09-09 4:17 ` Andrew Morton
2003-09-09 4:38 ` Ulrich Drepper [this message]
2003-09-09 5:56 ` Jeremy Fitzhardinge
2003-09-09 6:24 ` Roland McGrath
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=3F5D5946.1030002@redhat.com \
--to=drepper@redhat.com \
--cc=akpm@osdl.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=roland@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.