From: Rical Jasan <rj@2c3t.io>
To: Zack Weinberg <zackw@panix.com>
Cc: libc-alpha@sourceware.org, carlos@redhat.com, fweimer@redhat.com
Subject: Re: [PATCH 1/4] Reorganize manual sections on cryptography and random numbers.
Date: Wed, 09 May 2018 11:36:00 -0000 [thread overview]
Message-ID: <9ac245bd-0862-9ee8-0c66-aa5af416d4fc@2c3t.io> (raw)
In-Reply-To: <20180506175153.22629-2-zackw@panix.com>
On 05/06/2018 10:51 AM, Zack Weinberg wrote:
> In preparation for improvements to the discussion of cryptography,
> password handling, and random number generation, reorganize the
> sections of the manual that deal with these topics. This patch
> neither deletes any old text nor introduces any new text; it only
> moves text around. The description of 'getpass' moves to
> terminal.texi, since all it does is read a password from the
> controlling terminal with echo disabled. The pseudo-random number
> generator sections from math.texi and the "Unpredictable Bytes"
> section of crypt.texi are moved to a new file random.texi. Also, it
> is no longer true that crypt.texi's top @node needs to have no pointers.
>
> * manual/crypt.texi: Move most of the introductory text to the
> 'crypt' section. Move the example programs below the
> @deftypefun for 'crypt_r'. Move the DESERR_* table and
> DES_FAILED deftypefun below cbc_crypt. Move the entire
> 'getpass' section...
> * manual/terminal.texi: ...here.
>
> * manual/random.texi: New file consolidating all discussion of
> random number generation.
> * manual/crypt.texi: 'Unpredictable Bytes' section moved to random.texi.
> * manual/math.texi: 'Pseudo-Random Numbers' section moved to
> random.texi.
> * manual/Makefile (chapters): Add 'random' after 'arith'.
> * manual/arith.texi, manual/time.texi: Update chapter-level node
> pointers.
This is a great high-level overview of a largely mechanical change.
Other than minor, necessary changes to keep the manual somewhat
cohesive, this appears to be a copy/paste to me (yes, I took the time).
Thank you,
Rical
next prev parent reply other threads:[~2018-05-09 11:36 UTC|newest]
Thread overview: 19+ 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 1/4] Reorganize manual sections on cryptography and random numbers 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 [this message]
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
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-08 22:56 ` [PATCH 0/4 v3] Revise crypto documentation, deprecate DES, add --disable-crypt Rical Jasan
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=9ac245bd-0862-9ee8-0c66-aa5af416d4fc@2c3t.io \
--to=rj@2c3t.io \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--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).