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 23, 2025, 17:32 UTC
Message-ID
<xmqqfrb9v814.fsf@gitster.g>
In-Reply-To
<xmqqv7ki1xf1.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
Show 17 quoted lines
> I do not have strong preference either way.  Even if the wording is
> firm, it is really up to each contributor to honor the guideline and
> be honest with us.  You may see autocorrection in your editor fix a
> typo for you, and more advanced tools may offer to rewrite what you
> wrote, whether it is prose or code.  It is very plausible that,
> especially for simple fixes, the result may be what the contributor
> would have arrived on their own anyway, and in such a case, even the
> contributor would not even know how much came from "AI" or simple
> dictionary, or if that AI learned with things you should not have
> seen.
>
> So, I do not think it makes too big a difference in practice whether
> we adopt the QEMU with minimum rewrite, or the version you posted.
> As the one you sent is in line with what we give applicants of our
> mentoring programs, and it was read over by our SFC lawyer, I'd
> prefer to keep the version I already have in my tree.  Not moving on
> either, I think, is worse than adopting either in this case.

Taking time to discuss before deciding on an important issue is one thing, but waiting for more input to happen and not moving in either direction is worse than picking one and move on. As I said above, I do not quite see material difference between either one in practice.

I guess it is time to make an executive decision to merge it down to 'next'. We can still tweak the language if we want, but it is more important to have a written policy to reject materials of unknown origin (whether it came from generative AI or not) than not having one while we wish to be able to pick the best policy, waiting for a better argument to come from somewhere.

As to Elijah's concern about grandfathering, I do not think it has much practical benefit to make such a declaration. If it turns out that older "contributions" had added something we shouldn't have, regardless of how it was generated (either from generative AI or a human contributor typing while unconciously recalling what they saw elsewhere), we may need to revert it anyway, so we will deal with it when it becomes an issue.

Previous: Junio C HamanoNext: Elijah Newren
Message 28 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.