[PATCH v2 0/2] help: include SHA build options in version info
- From
Justin Tobler <jltobler@gmail.com>
- Date
- Apr 1, 2025, 20:36 UTC
- Message-ID
- <20250401203630.285451-1-jltobler@gmail.com>
- In-Reply-To
- <20250328170121.157563-1-jltobler@gmail.com>
Greetings,
Additional information regarding how Git was built can be found via the `--build-options` flag for git-version(1). This currently does not include information about the SHA-1 and SHA-256 implementations Git is built with.
This short series adds build option info for the SHA-1, SHA-256, and non-crypto-SHA-1 (if any) implementations which may be useful for diagnostic purposes
Changes since V1:
- Each SHA backend is expected to define either `SHA1_BACKEND`,
`SHA1_UNSAFE_BACKEND`, or `SHA256_BACKEND` as appropriate.
These symbols are then used to print the SHA build options in
the additional version info. - The names of the build options are used instead of
human-readable names. - Appended "(No collision detection)" to warn about SHA1
backends without collision detection. - Renamed "unsafe-SHA-1" to "non-crypto-SHA-1" in the printed
build options.- Small updates to documentation.
Thanks, -Justin
Justin Tobler (2): help: include SHA implementation in version info help: include unsafe SHA-1 build info in version
Documentation/git-version.adoc | 6 ++++++ hash.h | 11 +++++++++++ help.c | 13 +++++++++++++ 3 files changed, 30 insertions(+)
base-commit: 683c54c999c301c2cd6f715c411407c413b1d84e
-- 2.49.0