From: Jeff King <peff@peff.net>
To: Peter Baumann <waste.manager@gmx.de>
Cc: Jez <jezreel@gmail.com>, Thomas Rast <trast@student.ethz.ch>,
Bo Yang <struggleyb.nku@gmail.com>,
git@vger.kernel.org
Subject: Re: In-depth git blame?
Date: Wed, 2 Mar 2011 16:34:37 -0500 [thread overview]
Message-ID: <20110302213437.GG20400@sigill.intra.peff.net> (raw)
In-Reply-To: <20110302212951.GB24660@m62s10.vlinux.de>
On Wed, Mar 02, 2011 at 10:29:51PM +0100, Peter Baumann wrote:
> > If you use "git gui blame" or "tig blame", both have a "blame from
> > parent commit" feature. This restarts the blame using the content as
> > it was just before the answer you just got, so you can recursively
> > dig. It's unfortunately a somewhat manual process.
> >
>
> Hm. I guess pressing 'B' will blame the parent commit in tig. But I
> can't figure out how to navigate back to the old commit (before
> pressing 'B')? Any hints appreciated!
No, it is "," (comma) from the blame viewer in tig to blame starting
from the parent of the blamed commit of the highlighted line.
Doing "B" will just re-blame starting at that commit, which will of
course give you the same answer (I think it is a global "go to blame
view", so it is more useful when you are _not_ in the blame viewer
already).
And if you are confused at any point, "h" should give you a
context-sensitive list of keystrokes.
-Peff
next prev parent reply other threads:[~2011-03-02 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 20:43 In-depth git blame? Jez
2011-03-02 21:15 ` Jeff King
2011-03-02 21:29 ` Peter Baumann
2011-03-02 21:34 ` Jeff King [this message]
2011-03-02 21:44 ` Peter Baumann
2011-03-02 21:50 ` Peter Baumann
2011-03-07 23:20 ` Jonas Fonseca
2011-03-08 6:48 ` Peter Baumann
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=20110302213437.GG20400@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jezreel@gmail.com \
--cc=struggleyb.nku@gmail.com \
--cc=trast@student.ethz.ch \
--cc=waste.manager@gmx.de \
/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).