From: Zack Weinberg <zackw@panix.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 4/4] New configure option --disable-crypt.
Date: Tue, 08 May 2018 15:22:00 -0000 [thread overview]
Message-ID: <CAKCAbMiqSemG2BvA86V_vVExzvocSUvgaafRSfUvndCeMNrjxw@mail.gmail.com> (raw)
In-Reply-To: <9919a8b0-e0b0-db8d-120f-55242a981713@redhat.com>
On Tue, May 8, 2018 at 11:00 AM, Florian Weimer <fweimer@redhat.com> wrote:
>> + header file 'crypt.h'. 'unistd.h' will still declare the function
>> + 'crypt', as required by POSIX. Using this option does not change
>> + the set of programs that may need to be linked with '-lcrypt'; it
>> + only means that the GNU C Library will not provide that library.
>
> Two spaces after dot; see below.
...
>> +Do not install the password-hashing library @file{libcrypt} or the
>> +header file @file{crypt.h}. @file{unistd.h} will still declare the
>> +function @code{crypt}, as required by POSIX. Using this option does
>> +not change the set of programs that may need to be linked with
>> +@option{-lcrypt}; it only means that @theglibc{} will not provide that
>> +library.
> You need to use “POSIX@.” instead of “POSIX.” here.
Will fix. Thanks for the extra-careful proofreading.
zw
next prev parent reply other threads:[~2018-05-08 15:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 17:52 [PATCH 0/4 v3] Revise crypto documentation, deprecate DES, add --disable-crypt Zack Weinberg
2018-05-06 17:51 ` [PATCH 3/4] Deprecate DES encryption functions Zack Weinberg
2018-05-08 14:33 ` Florian Weimer
2018-05-08 15:24 ` Zack Weinberg
2018-05-06 17:52 ` [PATCH 4/4] New configure option --disable-crypt Zack Weinberg
2018-05-08 15:00 ` Florian Weimer
2018-05-08 15:22 ` Zack Weinberg [this message]
2018-05-06 17:52 ` [PATCH 2/4] Revise manual sections on cryptography and random numbers Zack Weinberg
2018-05-08 14:23 ` Florian Weimer
2018-05-08 15:59 ` Zack Weinberg
2018-05-08 17:51 ` Florian Weimer
2018-05-09 11:36 ` Rical Jasan
2018-05-09 15:47 ` Joseph Myers
2018-05-06 17:52 ` [PATCH 1/4] Reorganize " Zack Weinberg
2018-05-08 13:29 ` Florian Weimer
2018-05-08 13:37 ` Zack Weinberg
2018-05-08 13:38 ` Florian Weimer
2018-05-09 11:36 ` Rical Jasan
2018-05-08 22:56 ` [PATCH 0/4 v3] Revise crypto documentation, deprecate DES, add --disable-crypt Rical Jasan
2018-05-21 17:39 [PATCH 0/4 v3] libcrypt phaseout Zack Weinberg
2018-05-21 17:39 ` [PATCH 4/4] New configure option --disable-crypt Zack Weinberg
2018-05-21 19:52 ` Joseph Myers
2018-05-21 22:07 ` Zack Weinberg
2018-05-21 22:34 ` Joseph Myers
2018-05-22 1:08 ` Zack Weinberg
2018-06-20 20:40 ` Florian Weimer
2018-06-20 22:48 ` Zack Weinberg
2018-06-21 9:31 ` Florian Weimer
2018-06-21 9:32 ` Florian Weimer
2018-06-28 18:52 ` 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=CAKCAbMiqSemG2BvA86V_vVExzvocSUvgaafRSfUvndCeMNrjxw@mail.gmail.com \
--to=zackw@panix.com \
--cc=fweimer@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).