From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: Git List <git@vger.kernel.org>,
Chandra Pratap <chandrapratap376@gmail.com>,
Chandra Pratap <chandrapratap3519@gmail.com>,
Jeff King <peff@peff.net>,
Kyle Lippincott <spectral@google.com>,
John Cai <johncai86@gmail.com>
Subject: Re: [PATCH 1/2] receive-pack: use find_commit_header() in check_cert_push_options()
Date: Mon, 12 Feb 2024 08:40:31 -0800 [thread overview]
Message-ID: <xmqq4jed8wlc.fsf@gitster.g> (raw)
In-Reply-To: <7b0a87f1-4693-480e-90d4-14675e9a5f01@web.de> ("René Scharfe"'s message of "Sat, 10 Feb 2024 08:42:48 +0100")
René Scharfe <l.s.r@web.de> writes:
> I just discovered 14570dc67d (wrapper: add function to compare strings
> with different NUL termination, 2020-05-25). Perhaps squash this in to
> simplify?
Oooh, xstrncmpz() seems to target this exact use case. Nice.
>
> ---
> builtin/receive-pack.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/builtin/receive-pack.c b/builtin/receive-pack.c
> index dbee508775..db65607485 100644
> --- a/builtin/receive-pack.c
> +++ b/builtin/receive-pack.c
> @@ -717,9 +717,8 @@ static int check_cert_push_options(const struct string_list *push_options)
> buf = option + optionlen + 1;
> options_seen++;
> if (options_seen > push_options->nr
> - || strncmp(push_options->items[options_seen - 1].string,
> - option, optionlen)
> - || push_options->items[options_seen - 1].string[optionlen])
> + || xstrncmpz(push_options->items[options_seen - 1].string,
> + option, optionlen))
> return 0;
> }
>
> --
> 2.43.0
prev parent reply other threads:[~2024-02-12 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 20:36 [PATCH 1/2] receive-pack: use find_commit_header() in check_cert_push_options() René Scharfe
2024-02-09 20:41 ` [PATCH 2/2] receive-pack: use find_commit_header() in check_nonce() René Scharfe
2024-02-09 22:18 ` Junio C Hamano
2024-06-19 17:13 ` [PATCH 3/2] commit: remove find_header_mem() René Scharfe
2024-06-19 17:31 ` Jeff King
2024-06-20 18:12 ` Junio C Hamano
2024-02-09 22:11 ` [PATCH 1/2] receive-pack: use find_commit_header() in check_cert_push_options() Junio C Hamano
2024-02-10 7:42 ` René Scharfe
2024-02-12 16:40 ` 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=xmqq4jed8wlc.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chandrapratap3519@gmail.com \
--cc=chandrapratap376@gmail.com \
--cc=git@vger.kernel.org \
--cc=johncai86@gmail.com \
--cc=l.s.r@web.de \
--cc=peff@peff.net \
--cc=spectral@google.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).