git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[RFD/BUG?] git show with tree/commit

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Apr 12, 2016, 15:33 UTC
Message-ID
<570D154D.6090006@drmicha.warpmail.net>
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

Next: Junio C Hamano
Message 1 of 6 in “[RFD/BUG?] git show with tree/commit”
  1. Michael J GruberApr 12, 2016
  2. Junio C HamanoApr 12, 2016
  3. Michael J GruberApr 13, 2016
  4. Michael J GruberApr 13, 2016
  5. Jeff KingApr 12, 2016
  6. Junio C HamanoApr 12, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.