diff options
| author | brian m. carlson <sandals@crustytoothpaste.net> | 2025-10-09 21:56:24 +0000 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2025-10-09 17:46:14 -0700 |
| commit | 51acda73d3ca96b763f0fca3d7b33b4beaef786d (patch) | |
| tree | 91bff081e3468b62982f48cf202d83e141d87923 /Documentation/fsck-msgids.adoc | |
| parent | b95c59e21e6afeddc56400e162e818a9312f04d2 (diff) | |
| download | git-51acda73d3ca96b763f0fca3d7b33b4beaef786d.tar.xz | |
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 <sandals@crustytoothpaste.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/fsck-msgids.adoc')
| -rw-r--r-- | Documentation/fsck-msgids.adoc | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/fsck-msgids.adoc b/Documentation/fsck-msgids.adoc index 0ba4f9a27e..52d9a8a811 100644 --- a/Documentation/fsck-msgids.adoc +++ b/Documentation/fsck-msgids.adoc @@ -10,6 +10,12 @@ `badFilemode`:: (INFO) A tree contains a bad filemode entry. +`badGpgsig`:: + (ERROR) A tag contains a bad (truncated) signature (e.g., `gpgsig`) header. + +`badHeaderContinuation`:: + (ERROR) A continuation header (such as for `gpgsig`) is unexpectedly truncated. + `badName`:: (ERROR) An author/committer name is empty. |