From: Stephen Bash Date: Mon, 12 Dec 2011 17:05:25 GMT Subject: Re: Git blame only current branch Message-ID: <5e2440c1-8d11-4d92-b42f-14169a62ced1@mail> In-Reply-To: <20111212165542.GA4802@sigill.intra.peff.net> ----- Original Message ----- > From: "Jeff King" > Sent: Monday, December 12, 2011 11:55:42 AM > Subject: Re: Git blame only current branch > > On Mon, Dec 12, 2011 at 10:24:47AM -0500, Stephen Bash wrote: > > > I'm curious if there's a method to make git blame merge commits > > that introduce code to the given branch rather than commits on > > the original (topic) branch? For example: > > Usually when you are interested in seeing merges like this in > git-log, you would use one of "--first-parent" or "--merges". > However, though "git blame" takes revision arguments, it does > its own traversal of the graph that does not respect those > options. My first thought was --first-parent, and was disappointed when I didn't find it in the blame documentation :) I think for my purposes --first-parent is better than --merges because there are non-merge commits on the branch(es) of interest (and thus I think the problem would become ill-posed in the --merges case). > Modifying it to do --first-parent is pretty easy: > ... snip ... That's pretty simple... I'll try to do a little testing this afternoon. Thanks! Stephen