From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Brandon Williams" <bmwill@google.com>,
"Jeff King" <peff@peff.net>, "Stefan Beller" <sbeller@google.com>,
"Marc Stevens" <marc@marc-stevens.nl>,
"Dan Shumow" <shumow@gmail.com>,
"brian m . carlson" <sandals@crustytoothpaste.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [PATCH 0/2] doc hash-function-transition: minor & major clarifications
Date: Mon, 26 Mar 2018 18:27:06 +0000 [thread overview]
Message-ID: <20180326182708.26551-1-avarab@gmail.com> (raw)
Having read through the hash-function-transition.txt again, a couple
of things jumped out at me:
Ævar Arnfjörð Bjarmason (2):
doc hash-function-transition: clarify how older gits die on NewHash
We weren't accurately describing how "git status" would die on NewHash
repos on new versions.
doc hash-function-transition: clarify what SHAttered means
I don't think we had a good summary of how SHA-1 vulnerabilities
overlap with concerns Git has, now that we've moved to the hardened
SHA-1.
I may very well have gotten this new summary subtly wrong though. So
please review.
.../technical/hash-function-transition.txt | 40 +++++++++++++++----
1 file changed, 32 insertions(+), 8 deletions(-)
--
2.16.2.804.g6dcf76e118
next reply other threads:[~2018-03-26 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 18:27 Ævar Arnfjörð Bjarmason [this message]
2018-03-26 18:27 ` [PATCH 1/2] doc hash-function-transition: clarify how older gits die on NewHash Ævar Arnfjörð Bjarmason
2018-03-26 18:27 ` [PATCH 2/2] doc hash-function-transition: clarify what SHAttered means Ævar Arnfjörð Bjarmason
2018-03-26 19:03 ` Eric Sunshine
2018-03-26 18:35 ` [PATCH 0/2] doc hash-function-transition: minor & major clarifications Stefan Beller
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=20180326182708.26551-1-avarab@gmail.com \
--to=avarab@gmail.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=marc@marc-stevens.nl \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=sbeller@google.com \
--cc=shumow@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 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 NNTP newsgroup(s).