git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Git Mailing List <git@vger.kernel.org>
Subject: [RFD/BUG?] git show with tree/commit
Date: Tue, 12 Apr 2016 17:33:33 +0200	[thread overview]
Message-ID: <570D154D.6090006@drmicha.warpmail.net> (raw)

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

             reply	other threads:[~2016-04-12 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 15:33 Michael J Gruber [this message]
2016-04-12 16:26 ` [RFD/BUG?] git show with tree/commit Junio C Hamano
2016-04-13  8:02   ` Michael J Gruber
2016-04-13  9:41     ` Michael J Gruber
2016-04-12 16:34 ` Jeff King
2016-04-12 16:50   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=570D154D.6090006@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).