summaryrefslogtreecommitdiff
path: root/t/t4018/css-common
diff options
context:
space:
mode:
authorLibravatar brian m. carlson <sandals@crustytoothpaste.net>2020-02-22 20:17:42 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2020-02-24 09:33:30 -0800
commit42d4e1d1128fa1cb56032ac58f65ea3dd1296a9a (patch)
treefe7a1954c437e62ebe0a5bb7f0f82ff8fb70c114 /t/t4018/css-common
parentworktree: allow repository version 1 (diff)
downloadtgif-42d4e1d1128fa1cb56032ac58f65ea3dd1296a9a.tar.xz
commit: use expected signature header for SHA-256
The transition plan anticipates that we will allow signatures using multiple algorithms in a single commit. In order to do so, we need to use a different header per algorithm so that it will be obvious over which data to compute the signature. The transition plan specifies that we should use "gpgsig-sha256", so wire up the commit code such that it can write and parse the current algorithm, and it can remove the headers for any algorithm when creating a new commit. Add tests to ensure that we write using the right header and that git fsck doesn't reject these commits. Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4018/css-common')
0 files changed, 0 insertions, 0 deletions