From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH 0/2] fixing a few function pointer mismatches
Date: Sat, 19 Aug 2023 19:51:23 -0400 [thread overview]
Message-ID: <20230819235123.GA600613@coredump.intra.peff.net> (raw)
I saw that clang-18 hit Debian unstable, so I did my usual "build and
see if it finds anything new to complain about". Here's the result. :)
Note that that first one is a regression in the upcoming v2.42, though I
suspect the fallout would not be very widespread (see comments in the
commit message).
[1/2]: fsck: use enum object_type for fsck_walk callback
[2/2]: hashmap: use expected signatures for comparison functions
builtin/fsck.c | 2 +-
compat/terminal.c | 10 ++++++----
range-diff.c | 11 +++++++----
3 files changed, 14 insertions(+), 9 deletions(-)
-Peff
next reply other threads:[~2023-08-20 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 23:51 Jeff King [this message]
2023-08-19 23:53 ` [PATCH 1/2] fsck: use enum object_type for fsck_walk callback Jeff King
2023-08-19 23:55 ` [PATCH 2/2] hashmap: use expected signatures for comparison functions Jeff King
2023-08-20 8:31 ` [PATCH 0/2] fixing a few function pointer mismatches 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=20230819235123.GA600613@coredump.intra.peff.net \
--to=peff@peff.net \
--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;
as well as URLs for NNTP newsgroup(s).