> From: Paul Smith <p...@mad-scientist.net>
> On Wed, 2013-03-27 at 13:51 -0400, Dale R. Worley wrote:
> > But it suggests that if the same change
> > was made in multiple ancestor commits, git-blame might be picking out
> > the commit with the latest modification time.
> I can see an argument to be made for both models of handling multiple
> commits with the same change: choosing either the newest (who changed it
> "last") or the oldest (who changed it "first"--assuming later changes
> were just copies of the earlier ones).
In my opinion, the "correct" method is to start with the current
commit, then check to see if the line is the same as in any of the
commit's parent commits. If so, step to the first such parent (in the
ordering of the parents). Repeat. Eventually you get to a commit
which has no parents containing the current state of the line. That
is the (a) commit that introduced the change.
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
For more options, visit https://groups.google.com/groups/opt_out.