| commit | 5f308a89d8c37a186d58beff88542df00bc67975 | |
| author | Patrick Steinhardt <ps@pks.im> | |
| Mon, 1 Mar 2021 09:43:47 +0000 (1 10:43 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 1 Mar 2021 17:02:01 +0000 (1 09:02 -0800) | ||
| tree | bc1067dc8ea05b5d9e3972ce8ada0b35bddb412f | treesnapshot (tar.gz zip) |
| parent | 225365fb5195e804274ab569ac3cc4919451dc7f | commitdiff |
githooks.txt: replace mentions of SHA-1 specific properties
The githooks(5) documentation states in several places that the hook
will receive a SHA-1 or hashes of 40 characters length. Given that we're
transitioning to a world where both SHA-1 and SHA-256 are supported,
this is inaccurate.
Fix the issue by replacing mentions of SHA-1 with "object name" and not
explicitly mentioning the hash size.
Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The githooks(5) documentation states in several places that the hook
will receive a SHA-1 or hashes of 40 characters length. Given that we're
transitioning to a world where both SHA-1 and SHA-256 are supported,
this is inaccurate.
Fix the issue by replacing mentions of SHA-1 with "object name" and not
explicitly mentioning the hash size.
Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/githooks.txt | diffblobblamehistory |