public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:catalyst_2 commit in: files/
Date: Sun,  9 Oct 2011 00:30:48 +0000 (UTC)	[thread overview]
Message-ID: <e5cc28eb5b96f50e5fb24d2b3ddd114c616c4540.robbat2@gentoo> (raw)

commit:     e5cc28eb5b96f50e5fb24d2b3ddd114c616c4540
Author:     Robin H. Johnson <robbat2 <AT> gentoo <DOT> org>
AuthorDate: Sat Oct  8 22:27:41 2011 +0000
Commit:     Robin H. Johnson <robbat2 <AT> gentoo <DOT> org>
CommitDate: Sun Oct  9 00:30:39 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=e5cc28eb

Update list of supported hashes.

---
 files/catalyst.conf |   14 ++++++++++----
 1 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/files/catalyst.conf b/files/catalyst.conf
index b4e2385..fbaaa3a 100644
--- a/files/catalyst.conf
+++ b/files/catalyst.conf
@@ -5,8 +5,11 @@
 
 # Creates a .DIGESTS file containing the hash output from any of the supported
 # options below.  Adding them all may take a long time.
-# Supported options: sha1, sha224, ripemd128, ripemd320, sha384, crc32,
-#	ripemd256, sha256, sha512, ripemd160, md5
+# Supported hashes:
+# adler32, crc32, crc32b, gost, haval128, haval160, haval192, haval224,
+# haval256, md2, md4, md5, ripemd128, ripemd160, ripemd256, ripemd320, sha1,
+# sha224, sha256, sha384, sha512, snefru128, snefru256, tiger, tiger128,
+# tiger160, whirlpool
 digests="md5 sha1"
 
 # Creates a .CONTENTS file listing the contents of the file. Pick from any of
@@ -34,8 +37,11 @@ envscript="/etc/catalyst/catalystrc"
 # Internal hash function catalyst should use for things like autoresume, 
 # seedcache, etc.  The default and fastest is crc32.  You should not ever need
 # to change this unless your OS does not support it.
-# Supported options: sha1, sha224, ripemd128, ripemd320, sha384, crc32,
-#	ripemd256, sha256, sha512, ripemd160, md5
+# Supported hashes:
+# adler32, crc32, crc32b, gost, haval128, haval160, haval192, haval224,
+# haval256, md2, md4, md5, ripemd128, ripemd160, ripemd256, ripemd320, sha1,
+# sha224, sha256, sha384, sha512, snefru128, snefru256, tiger, tiger128,
+# tiger160, whirlpool
 hash_function="crc32"
 
 # options set different build-time options for catalyst. Some examples are:



             reply	other threads:[~2011-10-09  0:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09  0:30 Robin H. Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-09  0:30 [gentoo-commits] proj/catalyst:catalyst_2 commit in: files/ Robin H. Johnson
2011-10-09  0:30 Robin H. Johnson

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=e5cc28eb5b96f50e5fb24d2b3ddd114c616c4540.robbat2@gentoo \
    --to=robbat2@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