From: Gatla Vishweshwar Reddy <gatlavishweshwarreddy26@gmail.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org,
Gatla Vishweshwar Reddy <gatlavishweshwarreddy26@gmail.com>
Subject: Re: [PATCH v10] show-branch: convert per-branch flags to commit-slab
Date: Fri, 24 Jul 2026 08:59:59 +0530 [thread overview]
Message-ID: <20260724033000.89682-1-gatlavishweshwarreddy26@gmail.com> (raw)
In-Reply-To: <20260723213316.89081-1-gatlavishweshwarreddy26@gmail.com>
While waiting for your signal to send the next version, I reviewed
the patch myself and found a few issues I want to address:
1. show_merge_base() has inconsistent indentation on the continuation
line — has_all_rev_flags() is indented with a tab instead of
spaces to align with the opening parenthesis. Should be:
if (!(commit->object.flags & UNINTERESTING) &&
has_all_rev_flags(commit, num_rev)) {
2. int _b is declared in the middle of the parents loop body in
join_revs(). It should be declared at the top of that scope.
3. Regarding the {} block in join_revs() — as I explained earlier,
it scopes commit_is_merge_base after mark_seen(). I can move the
declaration to the top of the while loop body and remove the {}
if you prefer that style.
4. Regarding test coverage — your footnote mentioned a gap since the
test suite missed the basic crash. Should I add a test that simply
runs git show-branch on two branches as a smoke test before sending
the next version?
Please let me know what other issues you spotted and what signal
you need from me before I send the next version.
Vishweshwar
next prev parent reply other threads:[~2026-07-24 3:30 UTC|newest]
Thread overview: 27+ 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
2026-07-17 10:34 ` Gatla Vishweshwar Reddy
2026-07-17 10:42 ` Patrick Steinhardt
2026-07-17 15:25 ` Junio C Hamano
2026-07-17 16:32 ` [PATCH v8] " Gatla Vishweshwar Reddy
2026-07-17 17:53 ` [PATCH v7] " Junio C Hamano
2026-07-17 22:44 ` [PATCH v9] " Gatla Vishweshwar Reddy
2026-07-21 18:51 ` Junio C Hamano
2026-07-21 20:30 ` [PATCH v10] " Gatla Vishweshwar Reddy
2026-07-23 20:44 ` Junio C Hamano
2026-07-23 21:33 ` Gatla Vishweshwar Reddy
2026-07-24 3:29 ` Gatla Vishweshwar Reddy [this message]
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=20260724033000.89682-1-gatlavishweshwarreddy26@gmail.com \
--to=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