From: "cui via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: cui <523516579@qq.com>, cuiweixie <cuiweixie@gmail.com>
Subject: [PATCH] fetch: fix wrong evaluation order in URL trailing-slash trimming
Date: Wed, 25 Feb 2026 02:00:57 +0000 [thread overview]
Message-ID: <pull.2211.git.git.1771984857879.gitgitgadget@gmail.com> (raw)
From: cuiweixie <cuiweixie@gmail.com>
if i == -1, url[i] will be UB.
Signed-off-by: cuiweixie <cuiweixie@gmail.com>
---
fetch: fix wrong evaluation order in URL trailing-slash trimming
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2211%2Fcuiweixie%2Fbugfix-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2211/cuiweixie/bugfix-v1
Pull-Request: https://github.com/git/git/pull/2211
builtin/fetch.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/fetch.c b/builtin/fetch.c
index a3bc7e9380..306138c6e5 100644
--- a/builtin/fetch.c
+++ b/builtin/fetch.c
@@ -722,7 +722,7 @@ static void display_state_init(struct display_state *display_state, struct ref *
display_state->url = xstrdup("foreign");
display_state->url_len = strlen(display_state->url);
- for (i = display_state->url_len - 1; display_state->url[i] == '/' && 0 <= i; i--)
+ for (i = display_state->url_len - 1; 0 <= i && display_state->url[i] == '/'; i--)
;
display_state->url_len = i + 1;
if (4 < i && !strncmp(".git", display_state->url + i - 3, 4))
base-commit: 7c02d39fc2ed2702223c7674f73150d9a7e61ba4
--
gitgitgadget
next reply other threads:[~2026-02-25 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 2:00 cui via GitGitGadget [this message]
2026-02-25 14:10 ` [PATCH] fetch: fix wrong evaluation order in URL trailing-slash trimming Jeff King
2026-02-25 15:36 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2026-02-23 10:07 cuiweixie
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=pull.2211.git.git.1771984857879.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=523516579@qq.com \
--cc=cuiweixie@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 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.