From: Michael J Gruber <git@drmicha.warpmail.net>
To: Kumar Appaiah <a.kumar@alumni.iitm.ac.in>
Cc: git@vger.kernel.org, Jonas Fonseca <fonseca@diku.dk>
Subject: Re: tig show <commit> not working anymore?
Date: Thu, 16 Sep 2010 15:52:18 +0200 [thread overview]
Message-ID: <4C922112.404@drmicha.warpmail.net> (raw)
In-Reply-To: <20100916125337.GG5785@bowser.ece.utexas.edu>
Kumar Appaiah venit, vidit, dixit 16.09.2010 14:53:
> Hi!
>
> I observed that, since commit
> 53c089443cd9885fa677becee4bf7ffd56c3c357, tig show <commit> doesn't
> seem to work the same way as I had expected it to. The documentation
> update doesn't seem to indicate that this was to be expected (or I
> didn't understand it properly). Could someone please confirm that
> tig show <commit> should actually do something similar to git show <commit> | tig ?
It seems that since that tig commit, "tig show <commit>" shows HEAD
rather than <commit>. OTOH, "tig <commit>" does navigate to <commit>.
The reason is that tig passes %(commit), not %(revargs), to git show for
the "show" subcommand, but the obvious simple patch breaks diff view. I
guess somewhere in the codepath one has to differentiate between those.
cc'ing Mr. Tig...
Michael
next prev parent reply other threads:[~2010-09-16 13:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 12:53 tig show <commit> not working anymore? Kumar Appaiah
2010-09-16 13:46 ` Stefan Naewe
2010-09-16 19:01 ` Kumar Appaiah
2010-09-16 13:47 ` Jonas Fonseca
2010-09-16 18:56 ` Kumar Appaiah
2010-09-16 13:52 ` Michael J Gruber [this message]
2010-09-16 13:59 ` Stefan Naewe
2010-09-16 19:03 ` Kumar Appaiah
2010-09-18 5:01 ` Kumar Appaiah
2010-09-18 14:47 ` Jonas Fonseca
2010-09-19 18:46 ` Jonas Fonseca
2010-09-20 4:25 ` Kumar Appaiah
2010-09-21 12:56 ` Jonas Fonseca
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=4C922112.404@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=a.kumar@alumni.iitm.ac.in \
--cc=fonseca@diku.dk \
--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).