From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Arnav Bhate" <bhatearnav@gmail.com>,
"Christian Fredrik Johnsen" <christian@johnsen.no>,
"Đoàn Trần Công Danh" <congdanhqx@gmail.com>,
"Elijah Newren" <newren@gmail.com>, "Jeff King" <peff@peff.net>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Karthik Nayak" <karthik.188@gmail.com>,
"Philippe Blain" <levraiphilippeblain@gmail.com>,
"Ramsay Jones" <ramsay@ramsayjones.plus.com>,
"Usman Akinyemi" <usmanakinyemi202@gmail.com>
Subject: Re: "What's cooking" interim report
Date: Fri, 11 Apr 2025 11:32:33 +0200 [thread overview]
Message-ID: <Z_jhsVJi5U0qinbp@pks.im> (raw)
In-Reply-To: <xmqqy0w9orsn.fsf@gitster.g>
On Wed, Apr 09, 2025 at 04:10:00PM -0700, Junio C Hamano wrote:
> [New Topics]
> * ps/object-file-cleanup (2025-04-08) 10 commits
> - object-store: merge "object-store-ll.h" and "object-store.h"
> - object-store: remove global array of cached objects
> - object: split out functions relating to object store subsystem
> - object-file: split out functions relating to index subsystem
> - object-file: split up concerns of `HASH_*` flags
> - object-file: split out functions relating to object store subsystem
> - object-file: move `xmmap()` into "wrapper.c"
> - object-file: move `git_open_cloexec()` to "compat/open.c"
> - object-file: move `safe_create_leading_directories()` into "dir.c"
> - Merge branch 'ps/object-wo-the-repository' into ps/object-file-cleanup
> (this branch uses ps/object-wo-the-repository.)
>
> Code clean-up.
>
> Will merge to 'next'?
> cf. <xmqqsemiteot.fsf@gitster.g>
> cf. <CABPp-BFv_WGVUexyQBHkCcyO0N+UQCcJ3eM9Oh6bP_ZCUkaxLw@mail.gmail.com>
> source: <20250408-pks-split-object-file-v1-0-f1fd50191143@pks.im>
I have sent out v2 just now to fix a single grammar issue in a commit
message as pointed out by Elijah. So I think it's ready.
> * ps/refname-avail-check-optim (2025-04-09) 1 commit
> - refs/packed: fix BUG when seeking refs with UTF-8 characters
>
> Incorrect sorting of refs with bytes with high-bit set on platforms
> with signed char led to a BUG, which has been corrected.
>
> Will merge to 'next'.
> cf. <20250404205740.GA780449@coredump.intra.peff.net>
> source: <20250404-b4-pks-packed-backend-seek-with-utf8-v1-1-6ceb694e3bd7@pks.im>
Yup, makes sense.
> * rj/build-tweaks (2025-04-09) 13 commits
> - config.mak.uname: set CSPRNG_METHOD to getrandom on Linux
> - config.mak.uname: add arc4random to the cygwin build
> - config.mak.uname: add sysinfo() configuration for cygwin
> - builtin/gc.c: correct RAM calculation when using sysinfo
> - config.mak.uname: add clock_gettime() to the cygwin build
> - config.mak.uname: add HAVE_GETDELIM to the cygwin section
> - config.mak.uname: only set NO_REGEX on cygwin for v1.7
> - config.mak.uname: add a note about NO_STRLCPY for Linux
> - Makefile: remove NEEDS_LIBRT build variable
> - meson.build: set default help format to html on windows
> - meson.build: only set build variables for non-default values
> - Makefile: only set some BASIC_CFLAGS when RUNTIME_PREFIX is set
> - meson.build: remove -DCURL_DISABLE_TYPECHECK
>
> Various build tweaks, including CSPRNG selection on some platforms.
>
> Comments?
> source: <cover.1743859985.git.ramsay@ramsayjones.plus.com>
I'm currently traveling, so I didn't yet have time to review this. But I
do plan to do so on Monday.
Patrick
prev parent reply other threads:[~2025-04-11 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 23:10 "What's cooking" interim report Junio C Hamano
2025-04-10 9:10 ` Karthik Nayak
2025-04-11 9:28 ` Patrick Steinhardt
2025-04-11 9:32 ` Patrick Steinhardt [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=Z_jhsVJi5U0qinbp@pks.im \
--to=ps@pks.im \
--cc=Johannes.Schindelin@gmx.de \
--cc=bhatearnav@gmail.com \
--cc=christian@johnsen.no \
--cc=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@gmail.com \
--cc=levraiphilippeblain@gmail.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
--cc=ramsay@ramsayjones.plus.com \
--cc=usmanakinyemi202@gmail.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).