From: Florian Weimer <fweimer@redhat.com>
To: Nikos Mavrogiannopoulos <nmav@redhat.com>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
Zack Weinberg <zackw@panix.com>, Rical Jasan <rj@2c3t.io>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/2] crypt.3, encrypt.3: Add notes about _XOPEN_CRYPT.
Date: Sat, 14 Apr 2018 21:56:53 +0200 [thread overview]
Message-ID: <6ef320c1-1c58-e5c2-f2ca-c857389b0366@redhat.com> (raw)
In-Reply-To: <CADh2w8SLYdUqLGak6tcpeO2=nMsDGE10BMDMb4q+2Py9tHaOdw@mail.gmail.com>
On 04/14/2018 09:11 PM, Nikos Mavrogiannopoulos wrote:
> What about the second part of the suggestion. The crypt.3 manpage
> currently suggests including <unistd.h>, with _XOPEN_SOURCE defined,
> and that does not work with current glibc.
Current Fedora glibc. We need to align the Fedora behavior with
upstream again, either by lobbying for an upstream change, or changing
Fedora back to how things were before.
Thanks,
Florian
next prev parent reply other threads:[~2018-04-14 19:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 19:05 [PATCH 2/2] crypt.3, encrypt.3: Add notes about _XOPEN_CRYPT Carlos O'Donell
2018-04-13 9:34 ` Michael Kerrisk (man-pages)
2018-04-13 13:22 ` Carlos O'Donell
2018-04-13 15:10 ` Carlos O'Donell
2018-04-13 19:24 ` Michael Kerrisk (man-pages)
2018-04-14 19:11 ` Nikos Mavrogiannopoulos
2018-04-14 19:56 ` Florian Weimer [this message]
2018-04-16 1:35 ` Zack Weinberg
2018-04-17 13:25 ` Nikos Mavrogiannopoulos
2018-04-17 13:31 ` Florian Weimer
2018-04-14 4:43 ` Rical Jasan
2018-04-14 5:39 ` Michael Kerrisk (man-pages)
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=6ef320c1-1c58-e5c2-f2ca-c857389b0366@redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=nmav@redhat.com \
--cc=rj@2c3t.io \
--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