From: Junio C Hamano <gitster@pobox.com>
To: "Chandra Pratap via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Torsten Bögershausen" <tboegi@web.de>,
"Chandra Pratap" <chandrapratap376@gmail.com>,
"Chandra Pratap" <chandrapratap3519@gmail.com>
Subject: Re: [PATCH v4] sideband.c: remove redundant 'NEEDSWORK' tag
Date: Thu, 28 Dec 2023 12:33:46 -0800 [thread overview]
Message-ID: <xmqq8r5egj85.fsf@gitster.g> (raw)
In-Reply-To: <pull.1625.v4.git.1703750460527.gitgitgadget@gmail.com> (Chandra Pratap via GitGitGadget's message of "Thu, 28 Dec 2023 08:01:00 +0000")
"Chandra Pratap via GitGitGadget" <gitgitgadget@gmail.com> writes:
> Subject: Re: [PATCH v4] sideband.c: remove redundant 'NEEDSWORK' tag
The reason for removal is not that it was redundant and we said the
same thing elsewhere. Rather, what it claimed to be necessary has
turned to be unwanted. So something like
Subject: sideband.c: update stale NEEDSWORK comment
If we really wanted to change the type of the parameter to this
function to "size_t", we should also update its callers to hold
the values they use to compute the parameter also in "size_t".
But in this callchain, "int" is wide enough. Avoid tempting
future developers into wasting their time on using "size_t"
around this function.
or along that line would be more appropriate, perhaps?
Thanks.
> From: Chandra Pratap <chandrapratap3519@gmail.com>
>
> Signed-off-by: Chandra Pratap <chandrapratap3519@gmail.com>
> ---
> sideband.c: replace int with size_t for clarity
>
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1625%2FChand-ra%2Fdusra-v4
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1625/Chand-ra/dusra-v4
> Pull-Request: https://github.com/gitgitgadget/git/pull/1625
>
> Range-diff vs v3:
>
> 1: 273415aa6a4 ! 1: 8c003256e5b sideband.c: remove redundant 'NEEDSWORK' tag
> @@ sideband.c: void list_config_color_sideband_slots(struct string_list *list, cons
> *
> - * NEEDSWORK: use "size_t n" instead for clarity.
> + * It is fine to use "int n" here instead of "size_t n" as all calls to this
> -+ * function pass an 'int' parameter.
> ++ * function pass an 'int' parameter. Additionally, the buffer involved in
> ++ * storing these 'int' values takes input from a packet via the pkt-line
> ++ * interface, which is capable of transferring only 64kB at a time.
> */
> static void maybe_colorize_sideband(struct strbuf *dest, const char *src, int n)
> {
>
>
> sideband.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/sideband.c b/sideband.c
> index 6cbfd391c47..266a67342be 100644
> --- a/sideband.c
> +++ b/sideband.c
> @@ -69,7 +69,10 @@ void list_config_color_sideband_slots(struct string_list *list, const char *pref
> * of the line. This should be called for a single line only, which is
> * passed as the first N characters of the SRC array.
> *
> - * NEEDSWORK: use "size_t n" instead for clarity.
> + * It is fine to use "int n" here instead of "size_t n" as all calls to this
> + * function pass an 'int' parameter. Additionally, the buffer involved in
> + * storing these 'int' values takes input from a packet via the pkt-line
> + * interface, which is capable of transferring only 64kB at a time.
> */
> static void maybe_colorize_sideband(struct strbuf *dest, const char *src, int n)
> {
>
> base-commit: 1a87c842ece327d03d08096395969aca5e0a6996
next prev parent reply other threads:[~2023-12-28 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 17:01 [PATCH] sideband.c: replace int with size_t for clarity Chandra Pratap via GitGitGadget
2023-12-22 17:57 ` Torsten Bögershausen
2023-12-22 18:27 ` Chandra Pratap
2023-12-22 18:39 ` Torsten Bögershausen
2023-12-22 19:01 ` Junio C Hamano
2024-01-02 22:31 ` Taylor Blau
2023-12-23 17:03 ` [PATCH v2] " Chandra Pratap via GitGitGadget
2023-12-27 10:20 ` [PATCH v3] sideband.c: remove redundant 'NEEDSWORK' tag Chandra Pratap via GitGitGadget
2023-12-27 22:22 ` Junio C Hamano
2023-12-28 8:01 ` [PATCH v4] " Chandra Pratap via GitGitGadget
2023-12-28 20:33 ` Junio C Hamano [this message]
2023-12-26 17:14 ` [PATCH] sideband.c: replace int with size_t for clarity 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=xmqq8r5egj85.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chandrapratap3519@gmail.com \
--cc=chandrapratap376@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=tboegi@web.de \
/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).