From: Zack Weinberg <zackw@panix.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
"Carlos O'Donell" <carlos@redhat.com>,
Nikos Mavrogiannopoulos <nmav@redhat.com>
Subject: Re: [PATCH] New configure option --disable-libcrypt.
Date: Mon, 16 Apr 2018 18:41:00 -0000 [thread overview]
Message-ID: <CAKCAbMikMBt1KObAePB2v3TuoyC_BKa4DXLyg5pkcT5Nqzxk-A@mail.gmail.com> (raw)
In-Reply-To: <CAKCAbMgbEBd1beqZ-UrVXW0T51LpL-n5i2YQwmHVS0x51X1vVw@mail.gmail.com>
On Mon, Apr 16, 2018 at 11:56 AM, Zack Weinberg <zackw@panix.com> wrote:
>
> p.s. Maybe someone with the ability to file Austin Group defect
> reports or interpretation requests or whatever they're called should
> request the formal deprecation of encrypt and setkey?
Turns out I have that ability! http://austingroupbugs.net/view.php?id=1192
next prev parent reply other threads:[~2018-04-16 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 1:36 Zack Weinberg
2018-04-16 15:11 ` Florian Weimer
2018-04-16 15:56 ` Zack Weinberg
2018-04-16 18:41 ` Zack Weinberg [this message]
2018-04-17 10:21 ` Florian Weimer
2018-04-18 13:43 ` Zack Weinberg
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=CAKCAbMikMBt1KObAePB2v3TuoyC_BKa4DXLyg5pkcT5Nqzxk-A@mail.gmail.com \
--to=zackw@panix.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nmav@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 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).