From: "Eric S. Raymond" <esr@thyrsus.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: RFC: Separate commit identification from Merkle hashing
Date: Mon, 20 May 2019 23:31:53 -0400 [thread overview]
Message-ID: <20190521033153.GA2909@thyrsus.com> (raw)
In-Reply-To: <20190521025813.GA175422@google.com>
Jonathan Nieder <jrnieder@gmail.com>:
> > I think it's a weakness, though, that most of it is written as though it
> > assumes only one hash transition will be necessary. (This is me thinking
> > on long timescales again.)
>
> Hm, can you point to what part of the doc suggested that? Best to make
> the text clearer, to avoid confusing the next person.
I will reread it with an editorial eye and try to come up with
concrete suggestions, perhaps a patch. My relative ignorance
should actually be helpful here.
> > The same technique (probably the
> > same code!) could be used to map the otherwise uninterpreted
> > commit-IDs I'm proposing to lookup keys.
>
> No, since Git relies on commit IDs for integrity checking. The hash
> function transition described in that document relies on
> round-tripping ability for the duration of the transition.
I do not quite understand this comment yet. But I don't think it
matters that I don't, and I will by the time I write any code. I
expect the worst case is that the separated IDs require a different
lookup table from the hashes, but will resolve at the same speed.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2019-05-21 3:31 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 [this message]
2019-05-23 19:09 ` Jakub Narebski
2019-05-23 20:09 ` Jonathan Nieder
2019-05-23 20:53 ` Eric S. Raymond
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=20190521033153.GA2909@thyrsus.com \
--to=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--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).