Re: Git: new feature suggestion

From: Jakub Narębski <jnareb@gmail.com>
Date: Jan 20, 2017, 11:18 UTC
Message-ID: <e9e988b6-290f-3160-222f-2762865fe508@gmail.com>
In-Reply-To: <CA+55aFz5Rnt8U3bpvgoHQSfjPrnxnMfWUGBbHW2XKiagKXga5w@mail.gmail.com>

W dniu 20.01.2017 o 01:26, Linus Torvalds pisze:

Show 12 quoted lines

> On Thu, Jan 19, 2017 at 1:48 PM, Jakub Narębski <jnareb@gmail.com> wrote:
>> W dniu 19.01.2017 o 19:39, Linus Torvalds pisze:
>>>
>>> You can do it in tig, but I suspect a more graphical tool might be better.
>>
>> Well, we do have "git gui blame".
> 
> Does that actually work for people? Because it really doesn't for me.
> 
> And I'm not just talking about the aesthetics of the thing, but the
> whole experience, and the whole "dig into parent" which just gives me
> an error message.

Strange. I had been using "git gui blame" _because_ of its "dig to parent" functionality, and it worked for me just fine.

The other thing that I like about "git gui blame" is that it shows both the commit that moved the fragment of code (via "git blame"), and the commit that created the fragment of code (via "git blame -C -C -w", I think).

Anyway, all of this (sub)discussion is about archeology, but what might be more important is automatic rename handling when integrating changes, be it git-am, git-merge, or something else...

-- 
Jakub Narębski