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

Re: [PATCH] blame: make diff algorithm configurable

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 22, 2025, 20:39 UTC
Message-ID
<xmqqfrbay8kw.fsf@gitster.g>
In-Reply-To
<d59a2f97-1a69-44f6-924e-7419e36329a0@delpeuch.eu>
Antonin Delpeuch <antonin@delpeuch.eu> writes:
Show 22 quoted lines
> On 20/10/2025 18:05, Junio C Hamano wrote:
>
>>>      If the general idea of this patch is judged worthwhile, I would be happy
>>>      to add tests to demonstrate the impact of the diff algorithm on blame
>>>      output.
>> Do not ever say this here.
>>
>> I've seen from time to time people ask "I am thinking of doing this;
>> will a patch be accepted?  If so, I'll work on it." before showing
>> any work, and my response always has been:
>>
>>   (1) We don't know how useful and interesting your contribution would
>>       be for our audience, until we see it; and
>>
>>   (2) If you truly believe in your work (find it useful, find writing
>>       it fun, etc.), that would be incentive enough for you to work
>>       on it, whether or not the result will land in my tree.  You
>>       should instead aim for something so brilliant that we would
>>       come to you begging for your permission to include it in our
>>       project.
>
> I am surprised by your reaction here, both by its substance and form.

Yeah, after sending it out, I realized that the canned response above was not fitting to this exact instance. I overreacted primarily because what I saw everything before that part was indication of a great new contributor, which made my dissapointment to see the dreaded "I will do this if this is accepted" even worse.

Your "this one lacks tests" is a bit different from what we sometimes see on this list that I react with the above canned response, which is "I want to do this great thing. If you promise you will accept this change, I'll work on it" without showing any detailed design or code. It is more like "I know we need test but I have shown the main part of the change. Am I going in the right direction?"

You certainly didn't deserve the above response.  Sorry about that.
Previous: Antonin DelpeuchNext: Phillip Wood
Message 4 of 32 in “blame: make diff algorithm configurable”
  1. blame: make diff algorithm configurableAntonin Delpeuch via GitGitGadget, Oct 20, 2025
  2. Junio C HamanoOct 20, 2025
  3. Antonin DelpeuchOct 22, 2025
  4. Junio C HamanoOct 22, 2025
  5. Phillip WoodOct 23, 2025
  6. blame: make diff algorithm configurableAntonin Delpeuch via GitGitGadget, Oct 28, 2025
  7. Junio C HamanoOct 28, 2025
  8. Antonin DelpeuchOct 28, 2025
  9. blame: make diff algorithm configurableAntonin Delpeuch via GitGitGadget, Oct 28, 2025
  10. Phillip WoodOct 29, 2025
  11. Junio C HamanoOct 29, 2025
  12. Antonin DelpeuchOct 30, 2025
  13. Phillip WoodOct 30, 2025
  14. 0/2 blame: make diff algorithm configurableAntonin Delpeuch via GitGitGadget, Nov 1, 2025
  15. 1/2 xdiff: add 'minimal' to XDF_DIFF_ALGORITHM_MASKAntonin Delpeuch via GitGitGadget, Nov 1, 2025
  16. Phillip WoodNov 3, 2025
  17. 2/2 blame: make diff algorithm configurableAntonin Delpeuch via GitGitGadget, Nov 1, 2025
  18. Phillip WoodNov 3, 2025
  19. Junio C HamanoNov 3, 2025
  20. Junio C HamanoNov 6, 2025
  21. 0/2 blame: make diff algorithm configurableAntonin Delpeuch via GitGitGadget, Nov 6, 2025
  22. 1/2 xdiff: add 'minimal' to XDF_DIFF_ALGORITHM_MASKAntonin Delpeuch via GitGitGadget, Nov 6, 2025
  23. Junio C HamanoNov 7, 2025
  24. 2/2 blame: make diff algorithm configurableAntonin Delpeuch via GitGitGadget, Nov 6, 2025
  25. Junio C HamanoNov 7, 2025
  26. Phillip WoodNov 7, 2025
  27. Junio C HamanoNov 17, 2025
  28. 0/2 blame: make diff algorithm configurableAntonin Delpeuch via GitGitGadget, Nov 17, 2025
  29. 1/2 xdiff: add 'minimal' to XDF_DIFF_ALGORITHM_MASKAntonin Delpeuch via GitGitGadget, Nov 17, 2025
  30. 2/2 blame: make diff algorithm configurableAntonin Delpeuch via GitGitGadget, Nov 17, 2025
  31. Phillip WoodNov 17, 2025
  32. Junio C HamanoNov 17, 2025

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.