On Thursday, May 17, 2018 at 6:56:14 PM UTC-4, Philip Oakley wrote:
>
> From: "Richard Smith" <[email protected] <javascript:>> 
> To: "Git for human beings" <[email protected] <javascript:>> 
> Sent: Thursday, May 17, 2018 4:16 PM 
> Subject: [git-users] Re-create git log -p behavior using difftool? 
>
>
> > Is there a way that I can use difftool in a git log -p type scenario? 
> > 
> > Basically I'd like to give it a commit range and then walk though the 
> > commits looking at the results in difftool. 
> > 
> > I know I can do this with several of the review tools but I'd like 
> > something local on my computer and one that I can specify the difftool 
> > since I use different difftools depending on what I'm doing. 
> > 
> Richard, 
>
> How do you see it operating in terms of handling multiple different 
> difftools in the one log command (e.g. range of commits with range of 
> differnt file types?) 
>
> do you have a pseudo example you could sketch out? 
>

Hi Philip, 

I wasn't thinking of different difftools in the same command line.  I was 
just meaning that sometimes i like to use meld vs kdiff3,  Sometimes one 
does a better job depending on what the changes are.  The file types would 
all be source files.  I'm not expecting it do be able to do binary.

I'm thinking of behavior that is essentially the same as mergetool -t 
<tool> when doing conflict resolution.

So git log --difftool=meld <commitish>

It would have the same behavior as git log -p but instead of using diff it 
would use meld and would ask you if you wanted to view the files one by one 
as it came across them.  The same behavior as what mergetool does. Only 
files that were modified in the commit would get diffed.

Does that help make what I want clearer?  It's sort the same thing as you 
would have with gitk, or say sourcetree and setting an external diff tool. 

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to