From: "Eric S. Raymond" <esr@thyrsus.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: RFC: Separate commit identification from Merkle hashing
Date: Thu, 23 May 2019 16:53:13 -0400 [thread overview]
Message-ID: <20190523205313.GB69096@thyrsus.com> (raw)
In-Reply-To: <20190523200929.GA70860@google.com>
Jonathan Nieder <jrnieder@gmail.com>:
> In other words, usually the benefit of supporting multiple hash
> functions as a reader is that you want the strength of the strongest
> of those hash functions and you need a migration path to get there.
> If you don't have a way to eventually drop support for the weaker
> hashes, then what benefit do you get from supporting multiple hash
> functions?
Not losing the capability to verify old parts of histories up to the
strength of the old hash algorithm. Not perfect, but better than nothing.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2019-05-23 20:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 1:32 RFC: Separate commit identification from Merkle hashing Eric S. Raymond
2019-05-21 1:57 ` Jonathan Nieder
2019-05-21 2:38 ` Eric S. Raymond
2019-05-21 2:58 ` Jonathan Nieder
2019-05-21 3:31 ` Eric S. Raymond
2019-05-23 19:09 ` Jakub Narebski
2019-05-23 20:09 ` Jonathan Nieder
2019-05-23 20:53 ` Eric S. Raymond [this message]
2019-05-23 20:50 ` Eric S. Raymond
2019-05-23 20:54 ` Jonathan Nieder
2019-05-23 21:19 ` Eric S. Raymond
2019-05-23 21:39 ` Randall S. Becker
2019-05-23 21:50 ` Ævar Arnfjörð Bjarmason
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190523205313.GB69096@thyrsus.com \
--to=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=jrnieder@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).