Commit f6534dbda47 (fsck: document msg-id, 2022-10-25) introduced the
various fsck errors/warnings/etc into documentation, but included a
duplicate entry for `gitmodulesLarge`.
Drop the latter one, ensuring that the `gitmodules`-related fsck msg-ids
stay in alphabetical order.
After applying this commit, the following shows that we have no more
duplicate entries:
perl -ne '
if (/^`([a-zA-Z]+)/) { $ids{$1}++ }
END { print "$_\n" for grep { $ids{$_} > 1 } keys %ids }' \
Documentation/fsck-msgids.txt
Signed-off-by: Taylor Blau <me@xxxxxxxxxxxx>
---
Documentation/fsck-msgids.txt | 3 ---
1 file changed, 3 deletions(-)
diff --git a/Documentation/fsck-msgids.txt b/Documentation/fsck-msgids.txt
index 5edc06c658..68b8bb492b 100644
--- a/Documentation/fsck-msgids.txt
+++ b/Documentation/fsck-msgids.txt
@@ -79,9 +79,6 @@
`gitmodulesParse`::
(INFO) Could not parse `.gitmodules` blob.
-`gitmodulesLarge`;
- (ERROR) `.gitmodules` blob is too large to parse.
-
`gitmodulesPath`::
(ERROR) `.gitmodules` path is invalid.
--
2.45.1.216.g4365c6fcf96
