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

Re: [PATCH] index-pack: speed up promisor link recording

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Aug 2, 2026, 22:32 UTC
Message-ID
<am_Fb79hCnwmRzjL@fruit.crustytoothpaste.net>
In-Reply-To
<CAFwoC-7wUzce_XvuviXZe=5eTxJ5yyCpz=vsOheWKPCnz9Kr4A@mail.gmail.com>
On 2026-08-02 at 22:12:16, Arijit Banerjee wrote:
Show 12 quoted lines
> Thanks, Brian. I am not trying to bypass the project's policy.
> 
> The investigation is in the same general spirit as the Git performance work
> being tracked here:
> https://openai-git-upstream.openai.chatgpt.site/
> 
> I do not claim to be an expert on this topic, but Codex appears to have found
> a material performance improvement of about 15% on end-to-end blobless clone
> times.
> 
> Would it be appropriate to treat the current submission as an RFC? It seems
> worth trying to preserve the technical result.

I don't think the project's policy prevents you from doing analysis and investigation with an LLM, although it does require you to verify the correctness of the results and be accountable for them. If, based on the analysis of the performance impact, you write some code without the use of an LLM that improves things, I think that would be allowed and probably welcome, assuming it is otherwise acceptable. Some contributors will be willing to review such a contribution and others will not, but it is not outside of the policy.

However, writing substantial code with an LLM doesn't appear to be allowed. The kinds of trivial changes that I think would be allowed to be generated would be things like fixing spelling errors or adding include guards to header files that lack them. Of course, these are also the kinds of things you could mostly fix with a small script, which is why they are generally considered so trivial as to be uncopyrightable.

So I think to have a patch accepted in this case, you would need to totally discard the existing patch and rewrite it by hand without recourse to the generated code.

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.

-- 
brian m. carlson (they/them)
Toronto, Ontario, CA
Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 9 in “index-pack: speed up promisor link recording”
  1. index-pack: speed up promisor link recordingArijit Banerjee via GitGitGadget, Aug 2, 2026
  2. brian m. carlsonAug 2, 2026
  3. Arijit BanerjeeAug 2, 2026
  4. Junio C HamanoAug 2, 2026
  5. brian m. carlsonAug 2, 2026
  6. Junio C HamanoAug 2, 2026
  7. Arijit BanerjeeAug 2, 2026
  8. brian m. carlsonAug 3, 2026
  9. Collin FunkAug 3, 2026

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.