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

Re: [PATCH v7] show-branch: convert per-branch flags to commit-slab

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 17, 2026, 15:25 UTC
Message-ID
<xmqqse5h63js.fsf@gitster.g>
In-Reply-To
<aloHDhoerEhIXxFA@pks.im>
Patrick Steinhardt <ps@pks.im> writes:
Show 22 quoted lines
> Hi Gatla,
>
> On Fri, Jul 17, 2026 at 04:04:54PM +0530, Gatla Vishweshwar Reddy wrote:
>> Hi Patrick,
>> 
>> I am a real person. I used AI help for structuring reply in that thread. I understand that is not
>> appropriate here and will write my own from now on.
>
> Okay. Using AI is fine to help you out, but the human-focussed bits
> should really rather be written in a way that it feels like we're
> talking to a human. We're a community here, and when you see text that
> is so obviously written by an AI it can get very frustrating eventually.
>
> We've seen a strong uptick in threads that are obviously AI generated,
> only, and at times it just feels like one is merely talking to a prompt.
> This just doesn't scale well, as it leads to constant iterations and
> back and forth without much thinking being involved. So we require the
> other side to stop every once in a while and invest the necessary time,
> too. Otherwise the community will simply stop working, and that doesn't
> serve anyone well.
>
> Sorry if I came across as harsh.
Thanks for saying this.
When viewed in that light, what the v7 patch does is extremely
incoherent.  It gives the impression of having been generated by an
automated assistant and sent without human oversight, or perhaps
drafted in a state of severe late-night exhaustion.  For instance,
the commit message claims to have lifted 'max_revs' completely, yet
the proposed documentation updates still reference a hard limit of
64.  It also removes the local definition of 'UNINTERESTING', even
though the comment immediately above it still advises our future
selves to migrate to the shared definition eventually.

It appears the automation was not used merely for structuring the reply; the changes in the patch itself show signs of having been generated and sent out without any human oversight X-<.

Previous: Patrick SteinhardtNext: Gatla Vishweshwar Reddy
Message 18 of 27 in “show-branch: convert object.flags usage to a commit-slab”
  1. show-branch: convert object.flags usage to a commit-slabGatla Vishweshwar Reddy, Jul 14, 2026
  2. show-branch: convert object.flags to commit-slab with uint64_tGatla Vishweshwar Reddy, Jul 14, 2026
  3. Junio C HamanoJul 14, 2026
  4. Jeff KingJul 14, 2026
  5. show-branch: convert per-branch flags to commit-slabGatla Vishweshwar Reddy, Jul 15, 2026
  6. Junio C HamanoJul 15, 2026
  7. show-branch: convert per-branch flags to commit-slabGatla Vishweshwar Reddy, Jul 15, 2026
  8. Patrick SteinhardtJul 15, 2026
  9. Junio C HamanoJul 15, 2026
  10. show-branch: convert per-branch flags to commit-slabGatla Vishweshwar Reddy, Jul 15, 2026
  11. Junio C HamanoJul 15, 2026
  12. show-branch: convert per-branch flags to commit-slabGatla Vishweshwar Reddy, Jul 15, 2026
  13. Junio C HamanoJul 17, 2026
  14. show-branch: convert per-branch flags to commit-slabGatla Vishweshwar Reddy, Jul 17, 2026
  15. Patrick SteinhardtJul 17, 2026
  16. Gatla Vishweshwar ReddyJul 17, 2026
  17. Patrick SteinhardtJul 17, 2026
  18. Junio C HamanoJul 17, 2026
  19. show-branch: convert per-branch flags to commit-slabGatla Vishweshwar Reddy, Jul 17, 2026
  20. Junio C HamanoJul 17, 2026
  21. show-branch: convert per-branch flags to commit-slabGatla Vishweshwar Reddy, Jul 17, 2026
  22. Junio C HamanoJul 21, 2026
  23. show-branch: convert per-branch flags to commit-slabGatla Vishweshwar Reddy, Jul 21, 2026
  24. Junio C HamanoJul 23, 2026
  25. Gatla Vishweshwar ReddyJul 23, 2026
  26. Gatla Vishweshwar ReddyJul 24, 2026
  27. Patrick SteinhardtJul 17, 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.