With current next, using any commit sha1:
$ git cat-file -p cab2cdadfda8e8e8631026443b11d3ed6e7ba517
tree 04050d37b1676ba8da277be1902513049b45413a
parent b673b5e7d121021f77768c736cd9f98d7b3b3967
parent 7b0d47b3b6b5b64e02a5aa06b0452cadcdb18355
...
$ git show cab2cdadfda8e8e8631026443b11d3ed6e7ba517:
tree cab2cdadfda8e8e8631026443b11d3ed6e7ba517:
.gitattributes
.gitignore
.mailmap
...
$ git show 04050d37b1676ba8da277be1902513049b45413a:
tree 04050d37b1676ba8da277be1902513049b45413a
.gitattributes
.gitignore
.mailmap
...
While it's clear to me what's going on, I'm wondering whether it's a
good idea that "git show" says "tree" in front of the unresolved
treeish, whether it's a tree, a commit or something else. I think it's
pretty confusing. Alternatives would be:
tree <resolved tree id> # here: 040...
treeish <treeish> # here: "treeish cab2c..."
tree <treeish>^{tree} # here: "tree cab2c^{tree}"
Cheers
Michael
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
