From: Johannes Sixt <j6t@kdbg.org>
To: Git Mailing List <git@vger.kernel.org>,
"brian m. carlson" <sandals@crustytoothpaste.net>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH] gitk: discourage AI contributions
Date: Sun, 23 Aug 2026 11:25:42 +0200 [thread overview]
Message-ID: <b4ce8b09-5faa-4e6e-af38-5384a71ae699@kdbg.org> (raw)
Since the provenance of code generated by AI cannot be tracked with
confidence, which would be necessary to sign off a contribution, tell
contributors not to use AI.
Signed-off-by: Johannes Sixt <j6t@kdbg.org>
---
Following a recent brief discussion[1] it looks like I should not
accept code for Gitk that was generated by AI even if the submitter
understands all of it. Should I discourage AI contributions outright
like this or would it overshoot the mark?
-- Hannes
[1] https://lore.kernel.org/git/aooRdiVdjovWSFiG@fruit.crustytoothpaste.net/T/#md44580584f30c9b3e3c9e23250baf08b7fd7fb0c
README.md | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/README.md b/README.md
index 2e30746..c402788 100644
--- a/README.md
+++ b/README.md
@@ -79,13 +79,14 @@ are also accepted.
All commits must be signed off (use `git commit --signoff`) and should
have commit messages prefixed with `gitk:`.
-Email Patches
--------------
-
Send patches to git@vger.kernel.org and CC j6t@kdbg.org. See the Git
project's [patch submission guidelines](https://git-scm.com/docs/SubmittingPatches)
for detailed instructions on creating and sending patches.
+Please do not submit work that originated from AI, because this project
+is down-streamed to the Git project, which has a rather
+[strict AI guideline](https://git-scm.com/docs/SubmittingPatches#ai).
+
License
=======
--
2.55.0.704.g7397dd7565
next reply other threads:[~2026-08-23 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 9:25 Johannes Sixt [this message]
2026-08-23 13:10 ` [PATCH] gitk: discourage AI contributions Weijie Yuan
2026-08-26 6:55 ` Weijie Yuan
2026-08-26 21:55 ` brian m. carlson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4ce8b09-5faa-4e6e-af38-5384a71ae699@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.