Re: [PATCH 2/2] doc hash-function-transition: pick SHA-256 as NewHash

2018-07-25 Thread brian m. carlson
On Wed, Jul 25, 2018 at 09:45:52AM -0700, Junio C Hamano wrote: > Ævar Arnfjörð Bjarmason writes: > > > @@ -125,19 +122,19 @@ Detailed Design > > --- > > Repository format extension > > ~~~ > > -A NewHash repository uses repository format version `1` (see >

Re: [PATCH 2/2] doc hash-function-transition: pick SHA-256 as NewHash

2018-07-25 Thread Junio C Hamano
Jonathan Nieder writes: > Regardless of how we spell it in prose, I think `sha256` as an > identifier in configuration is the spelling people will expect. For > example, gpg ("gpg --version") calls it SHA256. OK. > For what it's worth, I would be in favor of modifying the section > more heavil

Re: [PATCH 2/2] doc hash-function-transition: pick SHA-256 as NewHash

2018-07-25 Thread Jonathan Nieder
Hi, Junio C Hamano wrote: > Ævar Arnfjörð Bjarmason writes: >> The consensus on the mailing list seems to be that SHA-256 should be >> picked as our NewHash, see the "Hash algorithm analysis" thread as of >> [1]. Linus has come around to this choice and suggested Junio make the >> final pick, a

Re: [PATCH 2/2] doc hash-function-transition: pick SHA-256 as NewHash

2018-07-25 Thread Junio C Hamano
Ævar Arnfjörð Bjarmason writes: > @@ -125,19 +122,19 @@ Detailed Design > --- > Repository format extension > ~~~ > -A NewHash repository uses repository format version `1` (see > +A SHA-256 repository uses repository format version `1` (see > Documentatio

[PATCH 2/2] doc hash-function-transition: pick SHA-256 as NewHash

2018-07-25 Thread Ævar Arnfjörð Bjarmason
The consensus on the mailing list seems to be that SHA-256 should be picked as our NewHash, see the "Hash algorithm analysis" thread as of [1]. Linus has come around to this choice and suggested Junio make the final pick, and he's endorsed SHA-256 [3]. This follow-up change changes occurrences of