From: Patrick Steinhardt <ps@pks.im>
To: Gatla Vishweshwar Reddy <gatlavishweshwarreddy26@gmail.com>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH v7] show-branch: convert per-branch flags to commit-slab
Date: Fri, 17 Jul 2026 10:52:12 +0200 [thread overview]
Message-ID: <alntPJy2VwVK75qj@pks.im> (raw)
In-Reply-To: <20260717074208.61303-1-gatlavishweshwarreddy26@gmail.com>
On Fri, Jul 17, 2026 at 01:12:06PM +0530, Gatla Vishweshwar Reddy wrote:
> Thank you very much for the thorough and insightful review —
> the performance observation about subset checking and the
> suggestion to remove MAX_REVS entirely were both excellent
> points that significantly improve this patch.
Sorry, but are we merely chatting with an AI or is there a human
anywhere between us and the prompt? I feel like this thread is becoming
a waste of time.
Patrick
next prev parent reply other threads:[~2026-07-17 8:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 18:30 [PATCH] show-branch: convert object.flags usage to a commit-slab Gatla Vishweshwar Reddy
2026-07-14 20:01 ` [PATCH v2] show-branch: convert object.flags to commit-slab with uint64_t Gatla Vishweshwar Reddy
2026-07-14 20:41 ` Junio C Hamano
2026-07-14 22:00 ` Jeff King
2026-07-15 1:47 ` [PATCH v3] show-branch: convert per-branch flags to commit-slab Gatla Vishweshwar Reddy
2026-07-15 3:34 ` Junio C Hamano
2026-07-15 4:18 ` [PATCH v4] " Gatla Vishweshwar Reddy
2026-07-15 6:47 ` Patrick Steinhardt
2026-07-15 7:20 ` [PATCH v3] " Junio C Hamano
2026-07-15 12:01 ` [PATCH v5] " Gatla Vishweshwar Reddy
2026-07-15 17:17 ` Junio C Hamano
2026-07-15 18:42 ` [PATCH v6] " Gatla Vishweshwar Reddy
2026-07-17 6:00 ` Junio C Hamano
2026-07-17 7:42 ` [PATCH v7] " Gatla Vishweshwar Reddy
2026-07-17 8:52 ` Patrick Steinhardt [this message]
2026-07-17 10:34 ` Gatla Vishweshwar Reddy
2026-07-17 8:51 ` [PATCH v5] " Patrick Steinhardt
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=alntPJy2VwVK75qj@pks.im \
--to=ps@pks.im \
--cc=gatlavishweshwarreddy26@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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