git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v5 6/6] RFC blame: use a fingerprint heuristic to match ignored lines

From
David Kastrup <dak@gnu.org>
Date
Apr 7, 2019, 21:52 UTC
Message-ID
<8736mtqy9n.fsf@fencepost.gnu.org>
In-Reply-To
<20190407214635.12984-1-michael@platin.gs>
michael@platin.gs writes:
Show 9 quoted lines
> From: Michael Platings <michael@platin.gs>
>
> Hi Barret,
> This is the updated fuzzy matching algorithm, sorry for the delay. It does
> highlight a bug in the calculation for the number of lines ("int nr_parent_lines
>  = e->num_lines - delta;") - if you apply the patch, build it, then try to
> ./git blame --ignore-rev <the patch commit ID> blame.c then you'll get a segfault
> because nr_parent_lines is a negative number. I haven't had time to investigate further
> but I have confirmed that the bug is not due to my patch.

If you segfault with the patch and don't segfault with the patch, there is not much of a point in declaring this "somebody else's problem", is there? It has to be fixed anyway in order to make the patch get in.

Or am I fundamentally misunderstanding something here?
-- 
David Kastrup
Previous: michael@platin.gsNext: Michael Platings
Message 2 of 7 in “RE: [PATCH v5 6/6] RFC blame: use a fingerprint heuristic to match ignored lines”
  1. michael@platin.gsApr 7, 2019
  2. David KastrupApr 7, 2019
  3. Michael PlatingsApr 8, 2019
  4. Barret RhodenApr 8, 2019
  5. Junio C HamanoApr 9, 2019
  6. Barret RhodenApr 9, 2019
  7. Barret RhodenApr 9, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.