From 1b84b06bc69580427d98e2e7e8e20a99b8bd1f43 Mon Sep 17 00:00:00 2001 From: Bryce Kwon Date: Sat, 7 Nov 2026 16:33:01 -1000 Subject: Hold the mailmap to max-blob-size git's read_mailmap_blob inflates the whole blob, so a pusher could make every page of a repository read as much as they liked. git reads a note and the .gitmodules file whole as well, and capping those would mean bounding the lookups where the log, commit and tree pages make them, so the manual names them instead. Nothing tested that mailmap.file and mailmap.blob are ignored either. --- MANUAL.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'MANUAL.txt') diff --git a/MANUAL.txt b/MANUAL.txt index b78ca33..859514c 100644 --- a/MANUAL.txt +++ b/MANUAL.txt @@ -402,9 +402,11 @@ max-blob-size:: memory to serve. The tree page's file view, the blame page, a tracked readme, a snapshot signature and the raw "plain" and "blob" output all refuse a larger object rather than load it whole, and the diff and patch - pages show it as binary. Whatever this is set to, the tree page shows no - more than the first 64 KB of a binary file as a hex dump, and links a - larger one to its "plain" output. Set to "0" to disable the limit. + pages show it as binary. A larger .mailmap is not applied, though a note + shown with a commit and a .gitmodules file are still read whole. Whatever + this is set to, the tree page shows no more than the first 64 KB of a + binary file as a hex dump, and links a larger one to its "plain" output. + Set to "0" to disable the limit. Default value: "10240" (10 MB). max-commit-count:: -- cgit 2.12.1