From: Peter Baumann <waste.manager@gmx.de>
To: Jonas Fonseca <fonseca@diku.dk>
Cc: Jeff King <peff@peff.net>, 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: Tue, 8 Mar 2011 07:48:08 +0100 [thread overview]
Message-ID: <20110308064808.GF24660@m62s10.vlinux.de> (raw)
In-Reply-To: <AANLkTimLf1gS03j4p7G3CKQWJC-b+_+T=ktaZ5xcJtZc@mail.gmail.com>
On Mon, Mar 07, 2011 at 06:20:56PM -0500, Jonas Fonseca wrote:
> On Wed, Mar 2, 2011 at 16:44, Peter Baumann <waste.manager@gmx.de> wrote:
> > [ Cc Jonas, because he might know more about that ]
>
> ... although he arrives late in the discussion.
>
> > On Wed, Mar 02, 2011 at 04:34:37PM -0500, Jeff King wrote:
> >> On Wed, Mar 02, 2011 at 10:29:51PM +0100, Peter Baumann wrote:
> >>
> >> > 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.
> >>
> > Thx, I didn't know that. Your help is really appreciated!
>
> Pressing 'B' in the blame view reloads the blame view based on the
> line/commit, which is currently selected. And as Jeff points out ','
> reloads based on the parent of the current commit.
>
> Tig is very poor in terms of history (search, blame, commit) so
> there's is no 'back' button.
Ah. That explain I didn't find any. Thx.
-Peter
prev parent reply other threads:[~2011-03-08 6:48 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
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 [this message]
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=20110308064808.GF24660@m62s10.vlinux.de \
--to=waste.manager@gmx.de \
--cc=fonseca@diku.dk \
--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 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).