From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: ab/sha-makefile-doc (was: What's cooking in git.git (Nov 2022, #01; Thu, 3))
Date: Mon, 07 Nov 2022 22:24:04 +0100 [thread overview]
Message-ID: <221107.86wn86tq2e.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <Y2RldUHTwNzmez73@nand.local>
On Thu, Nov 03 2022, Taylor Blau wrote:
> * ab/sha-makefile-doc (2022-10-26) 9 commits
> - Makefile: discuss SHAttered in *_SHA{1,256} discussion
> - Makefile: document default SHA-1 backend on OSX
> - Makefile: document SHA-1 and SHA-256 default and selection order
> - Makefile: document default SHA-256 backend
> - Makefile: rephrase the discussion of *_SHA1 knobs
> - Makefile: create and use sections for "define" flag listing
> - Makefile: correct DC_SHA1 documentation
> - INSTALL: remove discussion of SHA-1 backends
> - Makefile: always (re)set DC_SHA1 on fallback
>
> Makefile comments updates and reordering to clarify knobs used to
> choose SHA implementations.
>
> Will merge to 'next'?
> source: <cover-v4-0.9-00000000000-20221026T145255Z-avarab@gmail.com>
There was one outstanding issue from Junio noted in the v4, I just sent
a v5 in that should address that & more:
https://lore.kernel.org/git/cover-v5-00.10-00000000000-20221107T211736Z-avarab@gmail.com/
So hopefully with that it's ready for 'next'. I have a trivial patch
queued after it to flip the default on OSX to use
sha1collisiondetection.
next prev parent reply other threads:[~2022-11-07 21:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 1:05 What's cooking in git.git (Nov 2022, #01; Thu, 3) Taylor Blau
2022-11-05 0:21 ` Philip Oakley
2022-11-05 0:26 ` Taylor Blau
2022-11-07 12:19 ` Philip Oakley
2022-11-08 21:49 ` Taylor Blau
2022-11-07 14:28 ` ab/config-multi-and-nonbool (was: What's cooking in git.git (Nov 2022, #01; Thu, 3)) Ævar Arnfjörð Bjarmason
2022-11-07 14:33 ` ab/make-bin-wrappers " Ævar Arnfjörð Bjarmason
2022-11-08 14:27 ` Jeff King
2022-11-08 21:52 ` Taylor Blau
2022-11-09 14:04 ` Jeff King
2022-11-07 21:14 ` ab/coccicheck-incremental " Ævar Arnfjörð Bjarmason
2022-11-08 21:53 ` Taylor Blau
2022-11-07 21:24 ` Ævar Arnfjörð Bjarmason [this message]
2022-11-08 14:13 ` ab/submodule-helper-prep-only " Ævar Arnfjörð Bjarmason
2022-11-08 22:04 ` Taylor Blau
2022-11-08 14:14 ` ab/cmake-nix-and-ci " Ævar Arnfjörð Bjarmason
2022-11-08 14:49 ` Phillip Wood
2022-11-08 14:22 ` ab/misc-hook-submodule-run-command " Æ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=221107.86wn86tq2e.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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.