From: Junio C Hamano <gitster@pobox.com>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Cc: git@vger.kernel.org, brad@comstyle.com, sandals@crustytoothpaste.net
Subject: Re: [PATCH v4 0/2] config.mak.uname: update settings for FreeBSD
Date: Wed, 02 Jul 2025 09:21:58 -0700 [thread overview]
Message-ID: <xmqqtt3uef6h.fsf@gitster.g> (raw)
In-Reply-To: <20250702093736.36074-1-carenas@gmail.com> ("Carlo Marcelo Arenas Belón"'s message of "Wed, 2 Jul 2025 02:37:34 -0700")
Carlo Marcelo Arenas Belón <carenas@gmail.com> writes:
> Modernize config.mak.uname defaults for FreeBSD to prioritize using the
> platform implementation of memmem().
>
> Carlo Marcelo Arenas Belón (2):
> config.mak.uname: set NO_MEMMEM only for functional version
> build: retire NO_UINTMAX_T
>
> Makefile | 5 -----
> config.mak.uname | 9 +++------
> configure.ac | 8 --------
> meson.build | 11 -----------
> 4 files changed, 3 insertions(+), 30 deletions(-)
Thanks. As far as I (without access to FreeBSD boxes) can see, the
patches look good---the changes are reasonable and well described.
Will replace the single patch from Brad.
Thanks.
next prev parent reply other threads:[~2025-07-02 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 13:52 [PATCH v2] config.mak.uname: update settings for FreeBSD Carlo Arenas
2025-06-12 16:48 ` brian m. carlson
2025-06-12 21:31 ` Carlo Marcelo Arenas Belón
2025-06-12 21:51 ` [PATCH v3] " Junio C Hamano
2025-06-12 22:30 ` Carlo Marcelo Arenas Belón
2025-06-12 22:37 ` Junio C Hamano
2025-07-02 9:37 ` [PATCH v4 0/2] " Carlo Marcelo Arenas Belón
2025-07-02 9:37 ` [PATCH v4 1/2] config.mak.uname: set NO_MEMMEM only for functional version Carlo Marcelo Arenas Belón
2025-07-02 9:37 ` [PATCH v4 2/2] build: retire NO_UINTMAX_T Carlo Marcelo Arenas Belón
2025-07-02 16:21 ` Junio C Hamano [this message]
2025-06-12 16:52 ` [PATCH v2] config.mak.uname: update settings for FreeBSD 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=xmqqtt3uef6h.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=brad@comstyle.com \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.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.