From 51acda73d3ca96b763f0fca3d7b33b4beaef786d Mon Sep 17 00:00:00 2001 From: "brian m. carlson" Date: Thu, 9 Oct 2025 21:56:24 +0000 Subject: fsck: consider gpgsig headers expected in tags When we're creating a tag, we want to make sure that gpgsig and gpgsig-sha256 headers are allowed for the commit. The default fsck behavior is to ignore the fact that they're left over, but some of our tests enable strict checking which flags them nonetheless. Add improved checking for these headers as well as documentation and several tests. Signed-off-by: brian m. carlson Signed-off-by: Junio C Hamano --- fsck.h | 2 ++ 1 file changed, 2 insertions(+) (limited to 'fsck.h') diff --git a/fsck.h b/fsck.h index dd7df3d5b3..c26616d7eb 100644 --- a/fsck.h +++ b/fsck.h @@ -25,9 +25,11 @@ enum fsck_msg_type { FUNC(NUL_IN_HEADER, FATAL) \ FUNC(UNTERMINATED_HEADER, FATAL) \ /* errors */ \ + FUNC(BAD_HEADER_CONTINUATION, ERROR) \ FUNC(BAD_DATE, ERROR) \ FUNC(BAD_DATE_OVERFLOW, ERROR) \ FUNC(BAD_EMAIL, ERROR) \ + FUNC(BAD_GPGSIG, ERROR) \ FUNC(BAD_NAME, ERROR) \ FUNC(BAD_OBJECT_SHA1, ERROR) \ FUNC(BAD_PACKED_REF_ENTRY, ERROR) \ -- cgit v1.3-5-g9baa