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

Re: [PATCH v2] SubmittingPatches: add section about AI

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 3, 2025, 16:20 UTC
Message-ID
<xmqqjz1cufcd.fsf@gitster.g>
In-Reply-To
<CAP8UFD3wc-aj27Q_kFXvknJrpa-ySWbZiPmNCTMboA08=HP+xw@mail.gmail.com>
Christian Couder <christian.couder@gmail.com> writes:
Show 14 quoted lines
>> A milder way to phrase this would be to jump directly to "we reject
>> what the sender cannot explain when asked about it".  "How does this
>> work?"  "Why is this a good thing to do?"  "Where did it come from?"
>> instead of saying "looks AI generated".
>>
>> It would sidestep the "who decides if it looks AI generated?" question.
>
> I don't think the "who decides if it looks AI generated?" question is
> very relevant. If someone says that a patch looks mostly AI generated
> and gives a good argument supporting this claim, it's the same as if
> someone gives any other good argument against the patch. In the end,
> the community and you decide if the argument is good enough and if the
> patch should be rejected based on that (and other arguments for and
> against the patch of course).

And then who plays the final arbiter? One can keep insisting on a patch that looks to me an apparent AI slop that it was what one wrote oneself, but you may find it a plausible that it was a human creation. Then what?

It is very much relevant to avoid such argument, because the point is irrelevant. We are trying to avoid accepting something the submitter has no rights to claim theirs, and requesting them to explain where it came from, how it works, etc. would be a better test than "does it look AI generated? to everybody?", wouldn't it?

Previous: Christian CouderNext: rsbecker@nexbridge.com
Message 16 of 34 in “SubmittingPatches: forbid use of genAI to generate changes”
  1. SubmittingPatches: forbid use of genAI to generate changesJunio C Hamano, Jun 30, 2025
  2. brian m. carlsonJun 30, 2025
  3. Collin FunkJun 30, 2025
  4. Christian CouderJul 1, 2025
  5. Christian CouderJul 1, 2025
  6. Junio C HamanoJul 1, 2025
  7. Junio C HamanoJul 1, 2025
  8. Christian CouderJul 8, 2025
  9. SubmittingPatches: add section about AIChristian Couder, Oct 1, 2025
  10. Chuck WolberOct 1, 2025
  11. brian m. carlsonOct 1, 2025
  12. Ben KnobleOct 2, 2025
  13. Christian CouderOct 3, 2025
  14. Junio C HamanoOct 1, 2025
  15. Christian CouderOct 3, 2025
  16. Junio C HamanoOct 3, 2025
  17. rsbecker@nexbridge.comOct 3, 2025
  18. Christian CouderOct 8, 2025
  19. brian m. carlsonOct 1, 2025
  20. Christian CouderOct 3, 2025
  21. Elijah NewrenOct 3, 2025
  22. brian m. carlsonOct 3, 2025
  23. Junio C HamanoOct 6, 2025
  24. Elijah NewrenOct 8, 2025
  25. Junio C HamanoOct 12, 2025
  26. Christian CouderOct 8, 2025
  27. Junio C HamanoOct 13, 2025
  28. Junio C HamanoOct 23, 2025
  29. Elijah NewrenOct 8, 2025
  30. Christian CouderOct 8, 2025
  31. Michal SuchánekOct 8, 2025
  32. Christian CouderOct 8, 2025
  33. Collin FunkOct 9, 2025
  34. Christian CouderOct 8, 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.