On 03/01, Ramsay Jones wrote: > > > On 28/02/18 23:30, Stefan Beller wrote: > > $ git hash-object --stdin -w -t commit <<EOF > > tree c70b4a33a0089f15eb3b38092832388d75293e86 > > parent 105d5b91138ced892765a84e771a061ede8d63b8 > > author Stefan Beller <sbeller@xxxxxxxxxx> 1519859216 -0800 > > committer Stefan Beller <sbeller@xxxxxxxxxx> 1519859216 -0800 > > tree 5495266479afc9a4bd9560e9feac465ed43fa63a > > test commit > > EOF > > 19abfc3bf1c5d782045acf23abdf7eed81e16669 > > $ git fsck |grep 19abfc3bf1c5d782045acf23abdf7eed81e16669 > > $ > > > > So it is technically possible to create a commit with two tree entries > > and fsck is not complaining. > > Hmm, it's a while since I looked at that code, but I don't think > you have a commit with two trees - the second 'tree <sha1>' line > is just part of the commit message, isn't it? > > ATB, > Ramsay Jones > Actually it doesn't look like it. The commit msg doesn't start till after an empty newline so that commit has an empty commit msg. Here's one which you can see the msg when passed to show: git hash-object --stdin -w -t commit <<EOF tree 76d269b57d3c4283922216f84a2850e99f561ccc parent fa0624f79f9d5765d09598b003124b3cf0b9acdb author Brandon Williams <bmwill@xxxxxxxxxx> 1519859216 -0800 committer Brandon Williams <bmwill@xxxxxxxxxx> 1519859216 -0800 tree 76d269b57d3c4283922216f84a2850e99f561ccc This is a test commit with multiple trees EOF Of course the extra tree is ignored, but fsck doesn't complain and show happily shows what it knows about. -- Brandon Williams
