From: "Hanno Böck" <hanno@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] glep-0075: Update for reference implementation
Date: Thu, 24 Oct 2019 23:00:53 +0200 [thread overview]
Message-ID: <20191024230053.258c8cfb@computer> (raw)
In-Reply-To: <w6gpnil6fpx.fsf@kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
On Thu, 24 Oct 2019 22:39:06 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:
> In the rationale section, one reason given for the choice of the hash
> algorithm (BLAKE2B) was to "avoid code duplication". Isn't that
> argument moot, if all hashes supported by Portage are implemented?
> (Or in other words, couldn't a faster hash function like MD5 be used?)
FWIW blake2b is faster than md5. That was one of the design goals [1].
[1] https://blake2.net/
--
Hanno Böck
https://hboeck.de/
mail/jabber: hanno@hboeck.de
GPG: FE73757FA60E4E21B937579FA5880072BBB51E42
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-10-24 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 11:50 [gentoo-dev] [PATCH] glep-0075: Update for reference implementation Michał Górny
2019-10-24 20:39 ` Ulrich Mueller
2019-10-24 21:00 ` Hanno Böck [this message]
2019-10-25 6:26 ` Michał Górny
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=20191024230053.258c8cfb@computer \
--to=hanno@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