From: Kumar Appaiah <a.kumar@alumni.iitm.ac.in>
To: Stefan Naewe <stefan.naewe@atlas-elektronik.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: tig show <commit> not working anymore?
Date: Thu, 16 Sep 2010 14:01:32 -0500 [thread overview]
Message-ID: <20100916190132.GK5785@bowser.ece.utexas.edu> (raw)
In-Reply-To: <4C921FAC.9000108@atlas-elektronik.com>
Dear Stefan,
On Thu, Sep 16, 2010 at 03:46:20PM +0200, Stefan Naewe wrote:
> On 9/16/2010 2:53 PM, Kumar Appaiah wrote:
> > 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 ?
> >
> > Thanks!
>
> Works as expected for me on Debian Linux 5.0.6 i686:
>
> $ git version
> git version 1.7.2.3
>
> $ git describe
> tig-0.16-11-gf1fe753
>
> and on Cygwin with the same tig version and "git version 1.7.2.3.msysgit.1"
>
> Your tig version, OS, etc. ?
Here are the details:
TIG_VERSION="0.16-11-gf1fe753"
[kumar@redsun ~/Software/tig/tig] git --version
git version 1.7.1
./tig show HEAD
./tig show HEAD^ # Both show me f1fe753be71ef3ce5abcbb16c2a359f97e5c7e7d
Now, if I check out 53c089443cd9885fa677becee4bf7ffd56c3c357^, then I
get back the expected behaviour.
Please let me know if I've made some mistake.
Thanks!
Kumar
next prev parent reply other threads:[~2010-09-16 19:01 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 [this message]
2010-09-16 13:47 ` Jonas Fonseca
2010-09-16 18:56 ` Kumar Appaiah
2010-09-16 13:52 ` Michael J Gruber
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=20100916190132.GK5785@bowser.ece.utexas.edu \
--to=a.kumar@alumni.iitm.ac.in \
--cc=git@vger.kernel.org \
--cc=stefan.naewe@atlas-elektronik.com \
/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).