public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Rical Jasan <rj@2c3t.io>
To: Zack Weinberg <zackw@panix.com>
Cc: libc-alpha@sourceware.org, carlos@redhat.com, fweimer@redhat.com,
	kukuk@suse.de
Subject: Re: [PATCH 2/4] Reorganize crypt.texi.
Date: Wed, 23 May 2018 05:23:00 -0000	[thread overview]
Message-ID: <9e91971a-a150-6a3c-643e-7af675c5a46c@2c3t.io> (raw)
In-Reply-To: <20180521173853.5172-3-zackw@panix.com>

On 05/21/2018 10:38 AM, Zack Weinberg wrote:
> In preparation for a major revision of the documentation for
> crypt(_r), getentropy, and getrandom, reorganize crypt.texi.  This
> patch does not change any text; it only deletes and moves text.

LGTM.

Rical

  reply	other threads:[~2018-05-23  5:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 17:39 [PATCH 0/4 v3] libcrypt phaseout Zack Weinberg
2018-05-21 17:39 ` [PATCH 1/4] Disallow use of DES encryption functions in new programs Zack Weinberg
2018-05-22  6:58   ` Florian Weimer
2018-05-23  3:37   ` Rical Jasan
2018-05-23 16:50     ` Joseph Myers
2018-05-21 17:39 ` [PATCH 3/4] Revise crypt.texi Zack Weinberg
2018-05-25  2:52   ` Rical Jasan
2018-06-25 12:21     ` Florian Weimer
2018-06-25 12:26   ` Florian Weimer
2018-05-21 17:39 ` [PATCH 2/4] Reorganize crypt.texi Zack Weinberg
2018-05-23  5:23   ` Rical Jasan [this message]
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=9e91971a-a150-6a3c-643e-7af675c5a46c@2c3t.io \
    --to=rj@2c3t.io \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=kukuk@suse.de \
    --cc=libc-alpha@sourceware.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).