All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: Arijit Banerjee <arijit@effectiveailabs.com>,
	 Arijit Banerjee via GitGitGadget <gitgitgadget@gmail.com>,
	 git@vger.kernel.org,  Jonathan Tan <jonathantanmy@fastmail.com>,
	 Patrick Steinhardt <ps@pks.im>,
	 Arijit Banerjee <arijit91@gmail.com>,
	 ttaylorr@openai.com
Subject: Re: [PATCH] index-pack: speed up promisor link recording
Date: Sun, 02 Aug 2026 15:52:26 -0700	[thread overview]
Message-ID: <xmqq7bm82l05.fsf@gitster.g> (raw)
In-Reply-To: <am_Fb79hCnwmRzjL@fruit.crustytoothpaste.net> (brian m. carlson's message of "Sun, 2 Aug 2026 22:32:16 +0000")

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

> I understand that the SubmittingPatches documentation is a bit long, but
> I do suggest giving it at least a glance so you know what to expect.  I
> think reading this sort of contributing documentation is more important
> than ever since, in the era of LLMs, projects tend to have strong
> opinions on what is and is not acceptable, not only just in terms of LLM
> usage, but in how code and documentation are to be written and
> formatted.

Amen.

Since we seem to be drawn into the AI policy discussion, are there
things that we should consider borrowing from policies battle-tested
by other projects?  I kind of like what LLVM has as "extractive
contributions are rejected (whether it is AI or not AI)", as we are
severely review-bandwidth limited these days.


  reply	other threads:[~2026-08-02 23:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02 21:33 [PATCH] index-pack: speed up promisor link recording Arijit Banerjee via GitGitGadget
2026-08-02 21:51 ` brian m. carlson
2026-08-02 22:20   ` Arijit Banerjee
     [not found]   ` <CAFwoC-7wUzce_XvuviXZe=5eTxJ5yyCpz=vsOheWKPCnz9Kr4A@mail.gmail.com>
2026-08-02 22:32     ` brian m. carlson
2026-08-02 22:52       ` Junio C Hamano [this message]
2026-08-02 23:19         ` Arijit Banerjee
2026-08-02 22:46   ` Junio C Hamano
     [not found]     ` <CAFwoC-6EvoD-u7oceETi90MJ-FQA2zihdkn1i1wckKfoYRTKOw@mail.gmail.com>
2026-08-03  0:31       ` brian m. carlson
2026-08-03  0:55         ` Collin Funk

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=xmqq7bm82l05.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=arijit91@gmail.com \
    --cc=arijit@effectiveailabs.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=jonathantanmy@fastmail.com \
    --cc=ps@pks.im \
    --cc=sandals@crustytoothpaste.net \
    --cc=ttaylorr@openai.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 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.