From: Junio C Hamano <gitster@pobox.com>
To: "Mansi Singh via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Mansi Singh <mansimaanu8627@gmail.com>
Subject: Re: [PATCH 0/2] repo: remove redundant variable shadow in stats_table_print_structure
Date: Mon, 09 Mar 2026 20:08:43 -0700 [thread overview]
Message-ID: <xmqqcy1cz8hw.fsf@gitster.g> (raw)
In-Reply-To: <pull.2062.git.1773109018.gitgitgadget@gmail.com> (Mansi Singh via GitGitGadget's message of "Tue, 10 Mar 2026 02:16:56 +0000")
"Mansi Singh via GitGitGadget" <gitgitgadget@gmail.com> writes:
> The variable i is declared in the outer scope of
> stats_table_print_structure() and then re-declared inside the loop,
> shadowing the outer one unnecessarily. Remove the redundant inner
> declaration to clean up the scope.
>
> Signed-off-by: Mansi Singh mansimaanu8627@gmail.com
The above sounds more like a description for a single patch, not a
cover letter.
Because we strongly encourage one patch doing only one thing and
doing it well, a commit log message for one of the patches in a
two-patch series rarely makes a good description for the whole
series.
But reading it again, which variable 'i' is it talking about? [2/2]
does address 'entry' that is declared in an inner scope, masking the
variable with the same name declared in an outer scope.
Stepping back a bit, I do not quite see the need for these two
patcches to form a single topic. They look pretty much totally
independent topics. Perhaps you're better off treating them as two
independent topics, each with a single patch.
> Mansi (1):
> t7605: use test_path_is_file instead of test -f
>
> Mansi Singh (1):
> repo: remove redundant variable shadow in stats_table_print_structure
Are these two patches from two different people?
Last time in https://lore.kernel.org/git/xmqqv7fjw6yx.fsf@gitster.g/
we had three names, and we now have only two, so that can be called
an improvement, but let's whittle them down to just one ;-).
Thanks.
prev parent reply other threads:[~2026-03-10 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 2:16 [PATCH 0/2] repo: remove redundant variable shadow in stats_table_print_structure Mansi Singh via GitGitGadget
2026-03-10 2:16 ` [PATCH 1/2] t7605: use test_path_is_file instead of test -f Mansi via GitGitGadget
2026-03-10 2:16 ` [PATCH 2/2] repo: remove redundant variable shadow in stats_table_print_structure Mansi Singh via GitGitGadget
2026-03-10 13:08 ` [PATCH 0/2] " K Jayatheerth
2026-03-10 3:08 ` Junio C Hamano [this message]
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=xmqqcy1cz8hw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=mansimaanu8627@gmail.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