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

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

From
Christian Couder <christian.couder@gmail.com>
Date
Oct 8, 2025, 07:30 UTC
Message-ID
<CAP8UFD3QUQpnUYGS1qtfGbxOynJrZ-Q5aPPyjb7oij-6YSx7Wg@mail.gmail.com>
In-Reply-To
<CABPp-BFcg9M=XjqGPd+akrUOqJqREBmE9+NvO1Q05r4pUcOmEQ@mail.gmail.com>
On Fri, Oct 3, 2025 at 10:48 PM Elijah Newren <newren@gmail.com> wrote:
>
> On Wed, Oct 1, 2025 at 2:37 PM brian m. carlson
> <sandals@crustytoothpaste.net> wrote:
Show 15 quoted lines
> > We could say something like this:
> >
> >   Please do not sign off your work if you’re using an LLM to contribute
> >   unless you have included copyright and license information for all the
> >   code used in that LLM.
>
> Would this mean that you wanted to ban contributions like d12166d3c8bb
> (Merge branch 'en/docfixes', 2023-10-23), available on the list over
> at https://lore.kernel.org/git/pull.1595.git.1696747527.gitgitgadget@gmail.com/
> ?   We don't need to go theoretical, I've already contributed such a
> patch series before -- 2 years ago -- and it was merged.  Granted,
> that was entirely documentation, and I called out the usage of AI in
> the cover letter, and I manually checked every change (discarding many
> of them) and split it into commits on my own, could easily explain any
> change and why it was good, etc.  And I was upfront about all of it.
This is a good example why we don't want to ban any use of generated AI. Thanks.
> If any use of AI is bad, do we need to revert that series?
Previous: Collin Funk
Message 34 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.