From: "Matt Turner" <mattst88@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:master commit in: doc/
Date: Sat, 16 May 2020 06:43:34 +0000 (UTC) [thread overview]
Message-ID: <1589504236.b0d2777092252988a72f30dc915db93eb4d993d0.mattst88@gentoo> (raw)
commit: b0d2777092252988a72f30dc915db93eb4d993d0
Author: Matt Turner <mattst88 <AT> gentoo <DOT> org>
AuthorDate: Thu May 14 02:16:07 2020 +0000
Commit: Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Fri May 15 00:57:16 2020 +0000
URL: https://gitweb.gentoo.org/proj/catalyst.git/commit/?id=b0d27770
doc: Merge SUPPORTED HASHES section into digests section
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 <AT> 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
next reply other threads:[~2020-05-16 6:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 6:43 Matt Turner [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-16 6:43 [gentoo-commits] proj/catalyst:master commit in: doc/ Matt Turner
2020-05-16 6:43 Matt Turner
2020-04-10 6:18 Matt Turner
2020-04-09 18:48 Matt Turner
2020-03-30 23:47 Matt Turner
2018-04-26 15:57 Richard Farina
2017-11-22 15:52 [gentoo-commits] proj/catalyst:pending " Brian Dolbec
2017-11-29 17:20 ` [gentoo-commits] proj/catalyst:master " Brian Dolbec
2017-03-11 2:35 Richard Farina
2015-10-28 16:50 Mike Frysinger
2015-02-26 20:12 Brian Dolbec
2014-01-03 5:03 [gentoo-commits] proj/catalyst:pending " Brian Dolbec
2014-01-06 2:00 ` [gentoo-commits] proj/catalyst:master " Brian Dolbec
2013-03-09 2:41 Matt Turner
2013-03-09 2:41 Matt Turner
2012-11-21 5:20 Matt Turner
2012-11-02 0:26 Richard Farina
2012-10-31 22:11 Richard Farina
2011-07-21 4:44 Matt Turner
2011-06-25 18:08 Sebastian Pipping
2011-06-25 18:08 Sebastian Pipping
2011-06-25 18:08 Sebastian Pipping
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=1589504236.b0d2777092252988a72f30dc915db93eb4d993d0.mattst88@gentoo \
--to=mattst88@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@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