You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 <sandals@crustytoothpaste.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
ret=report(options, oid, OBJ_TAG, FSCK_MSG_BAD_GPGSIG, "invalid format - unexpected end after 'gpgsig' or 'gpgsig-sha256' line");
1074
+
goto done;
1075
+
}
1076
+
buffer=eol+1;
1077
+
1078
+
while (buffer<buffer_end&&starts_with(buffer, " ")) {
1079
+
eol=memchr(buffer, '\n', buffer_end-buffer);
1080
+
if (!eol) {
1081
+
ret=report(options, oid, OBJ_TAG, FSCK_MSG_BAD_HEADER_CONTINUATION, "invalid format - unexpected end in 'gpgsig' or 'gpgsig-sha256' continuation line");
1082
+
goto done;
1083
+
}
1084
+
buffer=eol+1;
1085
+
}
1086
+
}
1087
+
1070
1088
if (buffer<buffer_end&& !starts_with(buffer, "\n")) {
0 commit comments