From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: Elia Pinto <gitter.spiros@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] use C99 declaration of variable in for() loop
Date: Thu, 15 Feb 2024 15:43:27 -0800 [thread overview]
Message-ID: <xmqqa5o1mgyo.fsf@gitster.g> (raw)
In-Reply-To: <Zc6abO6RV9RwpABR@tapette.crustytoothpaste.net> (brian m. carlson's message of "Thu, 15 Feb 2024 23:12:44 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> I will also say that sending one giant patch for this may be a bit hard
> to review. While I will defer to Junio's opinion as the maintainer, I
> would be more inclined to review this kind of series if it came in in
> smaller patches, a few at a time, in which case I would find it a
> welcome improvement.
True. As to the specific topic of using "for (int i = 0; ...)",
it is tedious to review for mistakes and 17000+ lines of patch is
not a way to do so. I do not think I would be able to spot a change
in behaviour caused by a hunk like this
int i = 3;
... after some operations ...
- for (i = 0; i < 5; i++)
+ for (int i = 0; i < 5; i++)
if (condition_on_i(i))
break;
... after some operations ...
return i;
after scanning similar changes for 1000+ times in a single huge
patch.
prev parent reply other threads:[~2024-02-15 23:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 9:42 [PATCH] use C99 declaration of variable in for() loop Elia Pinto
2024-02-15 17:33 ` Junio C Hamano
2024-02-15 18:17 ` Christian Couder
2024-02-15 18:49 ` Junio C Hamano
2024-02-15 18:56 ` Elia Pinto
2024-02-15 20:07 ` Junio C Hamano
2024-02-15 23:12 ` brian m. carlson
2024-02-15 23:43 ` 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=xmqqa5o1mgyo.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitter.spiros@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.