Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Jeff King <peff@peff.net>,  Tamir Duberstein <tamird@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH v2] describe: limit default ref iteration to tags
Date: Wed, 10 Jun 2026 10:43:07 -0700	[thread overview]
Message-ID: <xmqq4ijawatw.fsf@gitster.g> (raw)
In-Reply-To: <aika_Q0rWhcI6eXR@pks.im> (Patrick Steinhardt's message of "Wed, 10 Jun 2026 10:08:51 +0200")

Patrick Steinhardt <ps@pks.im> writes:

> I very much think that we should and even have to expect that
> contributors adapt, because if we don't we will basically reinforce
> whatever AI is doing right now and increase the load on reviewers even
> more.
>
> I also think that we should reserve the right to reject a patch series
> completely in case we notice that we're basically just talking to a
> middleman that sits between an AI prompt and us (please note that I
> don't refer to this patch series specifically, this is more of a general
> statement).

Sounds sensible.  Something like this may make a good starting
point.

diff --git c/Documentation/SubmittingPatches w/Documentation/SubmittingPatches
index 176567738d..2fd7f6f9e6 100644
--- c/Documentation/SubmittingPatches
+++ w/Documentation/SubmittingPatches
@@ -499,6 +499,12 @@ checking for obvious mistakes, things that can be improved, things
 that don’t match our style, guidelines or our feedback, before sending
 it to us.
 
+We reserve the right to reject a patch series completely when we
+notice that we are basically just talking to a middleman that sits
+between an AI prompt and us, without having a better understanding of
+the subject matter than the AI agent being used.
+
+
 [[git-tools]]
 === Generate your patch using Git tools out of your commits.
 

  reply	other threads:[~2026-06-10 17:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09  2:32 [PATCH v2] describe: limit default ref iteration to tags Tamir Duberstein
2026-06-09 11:09 ` Jeff King
2026-06-09 13:23   ` Junio C Hamano
2026-06-09 13:40   ` D. Ben Knoble
2026-06-09 14:44   ` Tamir Duberstein
2026-06-10 17:45     ` Junio C Hamano
2026-06-10  8:08   ` Patrick Steinhardt
2026-06-10 17:43     ` Junio C Hamano [this message]
2026-06-10 18:50 ` [PATCH v3] " Tamir Duberstein

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=xmqq4ijawatw.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=ps@pks.im \
    --cc=tamird@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox