From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Taylor Blau" <me@ttaylorr.com>, "René Scharfe" <l.s.r@web.de>,
"Git List" <git@vger.kernel.org>
Subject: Re: [PATCH] merge-recursive: use fspathcmp() in path_hashmap_cmp()
Date: Sun, 29 Aug 2021 17:10:25 -0700 [thread overview]
Message-ID: <xmqqo89f7pxq.fsf@gitster.g> (raw)
In-Reply-To: <YSv1XZJvYdYj1JtP@coredump.intra.peff.net> (Jeff King's message of "Sun, 29 Aug 2021 17:00:13 -0400")
Jeff King <peff@peff.net> writes:
>> - if (ignore_case)
>> - return strcasecmp(e1->key, key ? key : e2->key);
>> - else
>> - return strcmp(e1->key, key ? key : e2->key);
>> + return fspathcmp(e1->key, key ? key : e2->key);
>> }
>>
>> static struct test_entry *alloc_test_entry(unsigned int hash,
>
> Maybe also:
>
> diff --git a/dir.c b/dir.c
> index 03c4d21267..ee46290cbb 100644
> --- a/dir.c
> +++ b/dir.c
> @@ -669,9 +669,7 @@ int pl_hashmap_cmp(const void *unused_cmp_data,
> ? ee1->patternlen
> : ee2->patternlen;
>
> - if (ignore_case)
> - return strncasecmp(ee1->pattern, ee2->pattern, min_len);
> - return strncmp(ee1->pattern, ee2->pattern, min_len);
> + return fspathncmp(ee1->pattern, ee2->pattern, min_len);
> }
>
> static char *dup_and_filter_pattern(const char *pattern)
>
> This is fun. :)
Yes.
So we found three of them in the existing code. A Coccinelle rule
may be an overkill, I guess.
next prev parent reply other threads:[~2021-08-30 0:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 21:30 [PATCH] merge-recursive: use fspathcmp() in path_hashmap_cmp() René Scharfe
2021-08-29 20:21 ` Taylor Blau
2021-08-29 21:00 ` Jeff King
2021-08-30 0:10 ` Junio C Hamano [this message]
2021-08-30 15:09 ` René Scharfe
2021-08-30 18:19 ` Jeff King
2021-08-30 16:55 ` Junio C Hamano
2021-08-30 18:22 ` René Scharfe
2021-08-30 20:49 ` Jeff King
2021-09-11 16:08 ` René Scharfe
2021-09-13 11:37 ` Johannes Schindelin
2021-09-13 17:09 ` Jeff King
2021-09-13 19:58 ` Junio C Hamano
2021-09-14 10:18 ` Johannes Schindelin
2021-09-14 14:11 ` Jeff King
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=xmqqo89f7pxq.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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.