"Bell, Bob (ISG)" <Robert.Bell@xxxxxxxx> writes: > What did you do before the bug happened? (Steps to reproduce your issue) > Tree-less git partial clone: git clone --filter=tree:0 https://... > Remove the promisor to prevent retrieving more objects: git config --local --unset remote.origin.promisor At this point, your repository is officially corrupt, but it is a very effective way to demonstrate the underlying issue that exists even if your repository weren't corrupt. I do agree with you that "git show -s", without any other options like --diff-filter that affects the commit selection [*], should not have to look into its tree. Unlike "git log -p", it should not have to see the tree of the commit is the same or different from the tree of the parent commit in order to decide if the commit should be shown. The fact that it gave an error "attempting to read the tree" is your own making by corrupting your repository ;-), but it is done as an easy way to demonstrate the underlying issue, which is that it is suboptimal for it to try to access the tree of the commit in a case where it should not have to. Is this essentially the same issue as these? https://lore.kernel.org/git/YqEyh5opAaJxph2+@xxxxxxxxxxxxxxxxxxxxxxx/ https://lore.kernel.org/git/20250504082715.GA6257@xxxxxxxxxxxxxxxxxxxxxxx/ [Footnote] * "git show -s --diff-filter=D" on a commit that does not delete any paths is silent. "-s" merely says "do not show the output from the diff machinery". The same for pathspec, to wit: $ git commit --allow-empty -m empty $ git show -s . It asks "if there are any changes to paths that match the pathspec, show the commit but do not show the diff output".
