From: Joseph Myers <joseph@codesourcery.com>
To: Joe Simmons-Talbott <josimmon@redhat.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] posix: Deprecate group_member for Linux
Date: Mon, 16 Oct 2023 20:46:39 +0000 [thread overview]
Message-ID: <f0d9b9d8-a04f-44fe-8c2d-73696e219d@codesourcery.com> (raw)
In-Reply-To: <62ddf1c4-22e8-c796-6c5e-3de97579696e@codesourcery.com>
On Mon, 16 Oct 2023, Joseph Myers wrote:
> On Mon, 16 Oct 2023, Joe Simmons-Talbott wrote:
>
> > bits/group_member.h | 31 +++++++++++++++++++
>
> > sysdeps/unix/sysv/linux/group_member.h | 32 ++++++++++++++++++++
>
> Is it group_member.h or bits/group_member.h? I'd expect the former, but
> then the latter file is misnamed and the #include in unistd.h is wrong.
That is: I'd expect bits/group_member.h (the first one in the diffs), not
group_member.h.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2023-10-16 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 17:54 Joe Simmons-Talbott
2023-10-16 20:37 ` Joseph Myers
2023-10-16 20:46 ` Joseph Myers [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=f0d9b9d8-a04f-44fe-8c2d-73696e219d@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=josimmon@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).