From: Moumita <dhar61595@gmail.com>
To: git@vger.kernel.org
Cc: Moumita <dhar61595@gmail.com>
Subject: [PATCH 0/1] [GSOC] Use unsigned type for bit flags in commit-reach.c
Date: Thu, 13 Feb 2025 00:58:39 +0530 [thread overview]
Message-ID: <20250212192841.8321-1-dhar61595@gmail.com> (raw)
The `flags` variable holds multiple bitwise flags (PARENT1, PARENT2, STALE),these flags are defined using (1u << N), so maybe there will be no issues if it is changed from `int` to `unsigned int`
Moumita (1):
commit-reach: use unsigned int for flags in paint_down_to_common()
commit-reach.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.48.0
next reply other threads:[~2025-02-12 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 19:28 Moumita [this message]
2025-02-12 19:28 ` [PATCH 1/1] commit-reach: use unsigned int for flags in paint_down_to_common() Moumita
2025-02-12 21:16 ` [PATCH 0/1] [GSOC] Use unsigned type for bit flags in commit-reach.c Junio C Hamano
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=20250212192841.8321-1-dhar61595@gmail.com \
--to=dhar61595@gmail.com \
--cc=git@vger.kernel.org \
/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