Re: What's cooking in git.git (Jun 2017, #06; Thu, 22)

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 24, 2017, 00:37 UTC
Message-ID: <xmqq60fmb4q8.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CAGZ79kZyMUKPahTXOF7ds6zSvFKLrM2N78JKG-2+GRL5nnmuvA@mail.gmail.com>

Stefan Beller <sbeller@google.com> writes:

> * add some heuristic to omit small blobs, (empty lines, closing braces)
>   Maybe this is can be solved by not considering anything
>   that occurs multiple times?

I vaguely recall that we had to do something similar in "blame -C" where it tries to avoid passing blame for insignificant changes down as copied. But for the purpose of this "moved line coloring", excluding multiple copy destinations of the same thing may be a simpler and more robust solution. It will not catch "somebody stupidly removed one function and made two private copies", though.