From: Peter Baumann <waste.manager@gmx.de>
To: Jeff King <peff@peff.net>
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 22:29:51 +0100 [thread overview]
Message-ID: <20110302212951.GB24660@m62s10.vlinux.de> (raw)
In-Reply-To: <20110302211545.GD20400@sigill.intra.peff.net>
On Wed, Mar 02, 2011 at 04:15:45PM -0500, Jeff King wrote:
> On Wed, Mar 02, 2011 at 03:43:42PM -0500, Jez wrote:
>
> > Git-blame is useful, but sometimes I want to know the series of
> > commits that have affected a line -- not just the most recent one. Is
> > there a way to do this?
>
> 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!
-Peter
next prev parent reply other threads:[~2011-03-02 21:30 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 [this message]
2011-03-02 21:34 ` Jeff King
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=20110302212951.GB24660@m62s10.vlinux.de \
--to=waste.manager@gmx.de \
--cc=git@vger.kernel.org \
--cc=jezreel@gmail.com \
--cc=peff@peff.net \
--cc=struggleyb.nku@gmail.com \
--cc=trast@student.ethz.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.