Re: Understanding behavior of git blame -M

From: Duy Nguyen <pclouds@gmail.com>
Date: Aug 16, 2014, 00:06 UTC
Message-ID: <CACsJy8DhfUY7uL91UGZUbC4g7WsMKkmj+7BF3xZ9RZyf8NcB4g@mail.gmail.com>
In-Reply-To: <874mxderwj.fsf@fencepost.gnu.org>

On Fri, Aug 15, 2014 at 9:42 PM, David Kastrup <dak@gnu.org> wrote:

Show 9 quoted lines

> The function diff_hunks is a wrapper for the diff engine.  Putting the
> context length explicitly into this wrapper (rather than not passing an
> argument and just setting the context length to zero anyway in the
> function) clearly indicates that somebody _wanted_ it called with
> different values.
>
> There is no documentation or rationale in the file _why_ as far as
> I remember.  Maybe it can crash or end up in an infinite loop.  Maybe it
> could do so at one point of time but no longer does.

Not sure if it helps, but ctxlen = 1 seems to be added back in d24bba8 (git-pickaxe -M: blame line movements within a file. - 2006-10-19), if I track the changes correctly.

-- 
Duy