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 17:19:16 -0400 [thread overview]
Message-ID: <20190523211916.GA73150@thyrsus.com> (raw)
In-Reply-To: <20190523205457.GC70860@google.com>
Jonathan Nieder <jrnieder@gmail.com>:
> Honestly, I do think you have missed some fundamental issues.
> https://public-inbox.org/git/ab3222ab-9121-9534-1472-fac790bf08a4@gmail.com/
> discusses this further.
Have re-read. That was a different pair of proposals.
I have abandoned the idea of forcing timestamp uniqueness entirely - that was
a hack to define a canonical commit order, and my new RFC describes a better
way to get this.
I still think finer-grained timestamps would be a good idea, but that is
much less important than the different set of properties we can guarantee
via the new RFC.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2019-05-23 21:19 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
2019-05-23 20:50 ` Eric S. Raymond
2019-05-23 20:54 ` Jonathan Nieder
2019-05-23 21:19 ` Eric S. Raymond [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190523211916.GA73150@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.