From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: "Okhuomon Ajayi" <okhuomonajayi54@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] [Outreachy] patch-ids: fix const correctness
Date: Thu, 09 Oct 2025 17:45:44 -0700 [thread overview]
Message-ID: <xmqqwm53bn47.fsf@gitster.g> (raw)
In-Reply-To: <a299c0ea-8eeb-4a21-9924-ebd7c6f6e0bd@app.fastmail.com> (Kristoffer Haugsbakk's message of "Thu, 09 Oct 2025 23:46:48 +0200")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> On Thu, Oct 9, 2025, at 23:44, Okhuomon Ajayi wrote:
>> Fix const correctness warning in patch_id_neq() in patch-ids.c.
>> ---
>> patch-ids.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/patch-ids.c b/patch-ids.c
>> index a5683b462c..4a72c2cbe6 100644
>> --- a/patch-ids.c
>> +++ b/patch-ids.c
>> @@ -42,7 +42,7 @@ static int patch_id_neq(const void *cmpfn_data,
>> const void *keydata UNUSED)
>> {
>> /* NEEDSWORK: const correctness? */
>> - struct diff_options *opt = (void *)cmpfn_data;
>> + const struct diff_options *opt = (void *)cmpfn_data;
>> struct patch_id *a, *b;
>>
>> a = container_of(eptr, struct patch_id, ent);
>> --
>> 2.43.0
>
> Can’t the comment be removed now, though? If the cmit msg. says “Fix”.
And the proposed commit log message should describe what the problem
is, why it matters, and how the updated code is better than the
current state of the code.
next prev parent reply other threads:[~2025-10-10 0:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 21:44 [PATCH] [Outreachy] patch-ids: fix const correctness Okhuomon Ajayi
2025-10-09 21:46 ` Kristoffer Haugsbakk
2025-10-10 0:45 ` Junio C Hamano [this message]
2025-10-09 21:57 ` Okhuomon Ajayi
2025-10-09 23:49 ` Agatha Isabelle
2025-10-10 0:13 ` Okhuomon Ajayi
-- strict thread matches above, loose matches on Subject: below --
2025-10-13 16:53 Okhuomon Ajayi
2025-10-13 17:12 ` Junio C Hamano
2025-10-13 17:22 ` Okhuomon Ajayi
2025-10-13 17:29 ` Junio C Hamano
2025-10-13 18:14 ` Okhuomon Ajayi
2025-10-13 18:33 ` Junio C Hamano
2025-10-13 21:55 ` Okhuomon Ajayi
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=xmqqwm53bn47.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=okhuomonajayi54@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;
as well as URLs for NNTP newsgroup(s).