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

Re: [PATCH] reftable/record: bound an object record's offset count by its length

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 20, 2026, 15:08 UTC
Message-ID
<xmqqqzhkxve6.fsf@gitster.g>
In-Reply-To
<atcKOhm0Kd5XryAg@pks.im>
Patrick Steinhardt <ps@pks.im> writes:
Show 19 quoted lines
> It's hard to say. With AI-generated commit messages you very often have
> the feeling that you end up understanding everything and nothing. It
> just feels off in a way that is hard to describe, and consequently it's
> also hard to say what exactly needs changing.
>
> My typical suggestion is to not use AI to write your commit message at
> all and instead write it yourself. Commit messages have always been the
> place where you can demonstrate that you understand what you are doing
> as part of the patch by properly explaining it in a way that another
> human being understands it. And I think that role is becoming even more
> important now: in a world where we cannot trust that the contributor has
> the slightest understanding of what they are contributing, they need to
> go the extra mile to prove it to us by having a well-written explanation
> thereof.
>
> I know that this is putting more of a burden on contributors, and I'm
> not a fan of that. But I think it's becoming abundantly clear that AI
> does not really give open communities much of a choice, at least not if
> they want to keep standards high.

Putting more burden on the user is fine, and the AI output, when used correctly, can be not so bad.

Having said that, the real problem is that nobody seems to guide generative AI machinery well enough to make intelligible output. In order for a user to guide the machinery well enough, they must know what they want to discuss, and the output would be different from what a clueless and hands-off "here is a bug report from somewhere I saw, I do not understand the system well enough, solve it and describe the solution" prompt would result in.

Writing the first draft manually and having a machine check and correct typos and grammar is not a bad practice, as you remain in control of the overall structure and contents of the final result.

Going in the other direction? If you are not familiar with the area and are easily fooled by intelligent-sounding nonsense uttered by generative AI, correcting such nonsense into a usable shape would be difficult, and would make those on the receiving end who have to read it miserable.

By the way, I cannot help but wonder what happened to the AI policy discussion that the contributors' summit promised we would have soon. Who is organizing it?

Previous: Patrick SteinhardtNext: Patrick Steinhardt
Message 5 of 10 in “reftable/record: bound an object record's offset count by its length”
  1. reftable/record: bound an object record's offset count by its lengthMatthew Suozzo via GitGitGadget, Oct 14, 2026
  2. Patrick SteinhardtOct 19, 2026
  3. m@suozzo.coOct 19, 2026
  4. Patrick SteinhardtOct 20, 2026
  5. Junio C HamanoOct 20, 2026
  6. Patrick SteinhardtOct 20, 2026
  7. Aniket GuptaOct 20, 2026
  8. 0/2 reftable: widen allocation size arguments to uintmax_tMatthew Suozzo via GitGitGadget, Oct 21, 2026
  9. 1/2 Makefile: build the reftable record unit testsMatthew Suozzo via GitGitGadget, Oct 21, 2026
  10. 2/2 reftable/basics: widen allocation size arguments to uintmax_tMatthew Suozzo via GitGitGadget, Oct 21, 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.