From: Matt Turner <mattst88@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Cc: Matt Turner <mattst88@gentoo.org>
Subject: [gentoo-catalyst] [PATCH 3/8] doc: Merge SUPPORTED HASHES section into digests section
Date: Thu, 14 May 2020 23:09:56 -0700 [thread overview]
Message-ID: <20200515061001.2581484-3-mattst88@gentoo.org> (raw)
In-Reply-To: <20200515061001.2581484-1-mattst88@gentoo.org>
It made sense to have this as a separate section when there were
multiple configuration options (digests and hash_function) but
hash_function is now gone.
Signed-off-by: Matt Turner <mattst88@gentoo.org>
---
doc/catalyst-config.5.txt | 17 +++++++----------
1 file changed, 7 insertions(+), 10 deletions(-)
diff --git a/doc/catalyst-config.5.txt b/doc/catalyst-config.5.txt
index f17944b2..7ac9a2a3 100644
--- a/doc/catalyst-config.5.txt
+++ b/doc/catalyst-config.5.txt
@@ -38,8 +38,13 @@ Basic configuration
*digests*::
Create a `.DIGESTS` file containing the hash output from any of the
supported options below. Adding them all may take a long time.
-(example: `md5 sha1 sha512 whirlpool`). See the *SUPPORTED HASHES*
-section for a list of supported hashes.
+(example: `md5 sha1 sha512 whirlpool`). The set of supported hashes
+is dependent on the version of Python. To see the set of hashes
+supported by the version of Python in use, run
++
+---------------------------------
+$ python3 -c 'import hashlib; print(hashlib.algorithms_available)'
+---------------------------------
*envscript*::
Environment script location, which allows users to set options such as
@@ -154,14 +159,6 @@ takes place in RAM. This feature requires a pretty large tmpfs
much RAM everything will fail horribly and it is not our fault.
-SUPPORTED HASHES
-----------------
-The list of supported hashes is dependent on the version of Python. To
-see the list of hashes supported by the version of Python in use, run
-
- $ python3 -c 'import hashlib; print(hashlib.algorithms_available)'
-
-
BINARY PACKAGE DEPENDENCIES
---------------------------
This section is only important if you are using binary packages to
--
2.26.2
next prev parent reply other threads:[~2020-05-15 6:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 6:09 [gentoo-catalyst] [PATCH 1/8] doc: Remove extra asterisk Matt Turner
2020-05-15 6:09 ` [gentoo-catalyst] [PATCH 2/8] doc: Drop pre-EAPI-5 text Matt Turner
2020-05-15 6:09 ` Matt Turner [this message]
2020-05-15 6:09 ` [gentoo-catalyst] [PATCH 4/8] targets: Test for locale-gen Matt Turner
2020-05-15 6:09 ` [gentoo-catalyst] [PATCH 5/8] catalyst: Drop unnecessary clear_path() Matt Turner
2020-05-15 6:09 ` [gentoo-catalyst] [PATCH 6/8] catalyst: Add error checking to snapshot target Matt Turner
2020-05-15 6:10 ` [gentoo-catalyst] [PATCH 7/8] catalyst: Make parent directories of snapshots/ Matt Turner
2020-05-15 6:10 ` [gentoo-catalyst] [PATCH 8/8] catalyst: Explain the git gc config options Matt Turner
2020-05-16 1:51 ` [gentoo-catalyst] [PATCH 1/8] doc: Remove extra asterisk Brian Dolbec
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=20200515061001.2581484-3-mattst88@gentoo.org \
--to=mattst88@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.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