git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2025, #03; Fri, 11)
Date: Mon, 14 Apr 2025 06:34:11 -0700	[thread overview]
Message-ID: <xmqqcydesw8c.fsf@gitster.g> (raw)
In-Reply-To: <Z_zDposxyFf3xPZD@pks.im> (Patrick Steinhardt's message of "Mon, 14 Apr 2025 10:13:26 +0200")

Patrick Steinhardt <ps@pks.im> writes:

> On Fri, Apr 11, 2025 at 03:58:33PM -0700, Junio C Hamano wrote:
>> * ps/object-file-cleanup (2025-04-11) 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'.
>>  source: <20250411-pks-split-object-file-v2-0-2bea0c9033ae@pks.im>
>
> Let's wait a bit with this one. There's been a couple more review
> comments that I want to address before this is ready for next.

OK.

>> * 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 just reviewed this series. It looks mostly fine to me, but I do have
> one question regarding one of the Meson patches.

Thanks.

  reply	other threads:[~2025-04-14 13:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 22:58 What's cooking in git.git (Apr 2025, #03; Fri, 11) Junio C Hamano
2025-04-12 18:03 ` Philippe Blain
2025-04-13  2:55   ` Philippe Blain
2025-04-14 13:04   ` Junio C Hamano
2025-04-14  8:13 ` Patrick Steinhardt
2025-04-14 13:34   ` Junio C Hamano [this message]
2025-04-14 20:14   ` [-SPAM-] " Ramsay Jones
2025-04-14 11:03 ` ds/path-walk-2 (was Re: What's cooking in git.git (Apr 2025, #03; Fri, 11)) Derrick Stolee
2025-04-14 12:34   ` 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=xmqqcydesw8c.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /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).