Re: [PATCH 1/2] help: include SHA implementation in version info

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 1, 2025, 09:47 UTC
Message-ID: <xmqq1pucb4d9.fsf@gitster.g>
In-Reply-To: <Z-pCG9d7Rf9SMuXJ@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

Show 5 quoted lines

> Another option: we could ask the implementations themselves to define a
> symbol `SHA1_BACKEND` and use it here. This would automatically ensure
> that any implementation must define the symbol as we'd otherwise get a
> compile error. We could also conditionally define `SHA1_UNSAFE_BACKEND`
> depending on whether or not we have it.

Much simpler and less error prone.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.