mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: "Martin Ågren" <>
Cc: "brian m. carlson" <>,
	Git Mailing List <>
Subject: Re: [PATCH] Documentation: mark `--object-format=sha256` as experimental
Date: Thu, 13 Aug 2020 13:34:10 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> ("Martin =?utf-8?Q?=C3=85gren=22's?= message of "Sat, 8 Aug 2020 00:15:13 +0200")

Martin Ågren <> writes:

>> IOW, you question "if we go a few releases without any major issues"
>> part?  I tend to agree that for a large change like this, a few
>> releases may not be sufficiently long time for a feature that is
>> marked as experimental in big flashing red letters to get exercised
>> enough to get major issues noticed.
> Yeah, thanks for summarizing what I failed to express using so many
> words.
> I'm fully open to the idea that some people want to leave SHA-1 behind
> and that they can do it today, in some "local" sense. If those people
> are fully aware that they are guinea pigs, it might actually be ok for
> us to subject them to a few rounds of "oops, Git v2.32.0 produces data
> that v2.34.0 and later will barf on". Or at least it would be on our
> table whether we wanted to be that cavalier.
> Once SHA-256 repos as such are no longer experimental, I fear that we
> can only buy ourselves that leeway by introducing fiftyeleven different
> config flags for "please produce auxiliary files X even if you don't
> actually use them", "please do use X, and I'm fully expecting to trip on
> them if you decide to tweak them in backwards-incompatible ways", and so
> on. The alternative to buying such leeway might be to establish, pretty
> early on, a respectable set of things we support "for compatibility
> reasons".

OK, so can we resolve this one way or the other and move on?

For now, I'd vote for applying this warning patch, but with or
without such warning, it is more important to iron out those details
we fear might have to change.


  reply	other threads:[~2020-08-13 20:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 20:23 [PATCH] Documentation: mark `--object-format=sha256` as experimental Martin Ågren
2020-08-06 23:08 ` brian m. carlson
2020-08-07 14:08   ` Martin Ågren
2020-08-07 20:50     ` Junio C Hamano
2020-08-07 22:15       ` Martin Ågren
2020-08-13 20:34         ` Junio C Hamano [this message]
2020-08-14  0:51           ` brian m. carlson
2020-08-16 10:01             ` [PATCH v2] " Martin Ågren

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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

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).