From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Eric S. Raymond" <esr@thyrsus.com>, git@vger.kernel.org
Subject: Re: Finer timestamps and serialization in git
Date: Thu, 16 May 2019 00:14:44 -0400 [thread overview]
Message-ID: <20190516041444.GG4596@sigill.intra.peff.net> (raw)
In-Reply-To: <871s0zwjv0.fsf@evledraar.gmail.com>
On Wed, May 15, 2019 at 10:20:03PM +0200, Ævar Arnfjörð Bjarmason wrote:
> > Since this is going to have to happen anyway
>
> The SHA-1 <-> SHA-256 transition is planned to happen, but there's some
> strong opinions that this should be *only* for munging the content for
> hashing, not adding new stuff while we're at it (even if optional). See
> : https://public-inbox.org/git/87ftyyedqd.fsf@evledraar.gmail.com/
One reason for this is that the transition plan calls for being able to
convert between the sha1 and sha256 representations losslessly (which
makes interoperability possible and avoids a flag day). So even if the
sha256 format understood floating-point timestamps in the committer
header, we'd have to have some way of representing that same information
in the sha1 format. Which implies putting it into a new header, as you
described below.
And if it's in a new header in sha1, then is there any real advantage in
having it somewhere else in the sha256 version? I dunno. Maybe a little,
as eventually all of the sha1 formats would die off, after everybody has
transitioned.
-Peff
prev parent reply other threads:[~2019-05-16 4:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 19:16 Finer timestamps and serialization in git Eric S. Raymond
2019-05-15 20:16 ` Derrick Stolee
2019-05-15 20:28 ` Jason Pyeron
2019-05-15 21:14 ` Derrick Stolee
2019-05-15 22:07 ` Ævar Arnfjörð Bjarmason
2019-05-16 0:28 ` Eric S. Raymond
2019-05-16 1:25 ` Derrick Stolee
2019-05-20 15:05 ` Michal Suchánek
2019-05-20 16:36 ` Eric S. Raymond
2019-05-20 17:22 ` Derrick Stolee
2019-05-20 21:32 ` Eric S. Raymond
2019-05-15 23:40 ` Eric S. Raymond
2019-05-19 0:16 ` Philip Oakley
2019-05-19 4:09 ` Eric S. Raymond
2019-05-19 10:07 ` Philip Oakley
2019-05-15 23:32 ` Eric S. Raymond
2019-05-16 1:14 ` Derrick Stolee
2019-05-16 9:50 ` Ævar Arnfjörð Bjarmason
2019-05-19 23:15 ` Jakub Narebski
2019-05-20 0:45 ` Eric S. Raymond
2019-05-20 9:43 ` Jakub Narebski
2019-05-20 10:08 ` Ævar Arnfjörð Bjarmason
2019-05-20 12:40 ` Jeff King
2019-05-20 14:14 ` Eric S. Raymond
2019-05-20 14:41 ` Michal Suchánek
2019-05-20 22:18 ` Philip Oakley
2019-05-20 21:38 ` Elijah Newren
2019-05-20 23:12 ` Eric S. Raymond
2019-05-21 0:08 ` Jakub Narebski
2019-05-21 1:05 ` Eric S. Raymond
2019-05-15 20:20 ` Ævar Arnfjörð Bjarmason
2019-05-16 0:35 ` Eric S. Raymond
2019-05-16 4:14 ` Jeff King [this message]
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=20190516041444.GG4596@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.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.
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).