All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,  git@vger.kernel.org
Subject: Re: ps/reftable-sans-compat-util, was Re: What's cooking in git.git (Feb 2025, #09; Fri, 28)
Date: Sat, 29 Mar 2025 16:56:45 -0700	[thread overview]
Message-ID: <xmqqplhzbdc2.fsf@gitster.g> (raw)
In-Reply-To: <Z-Y1YbE2EVqLZhGO@pks.im> (Patrick Steinhardt's message of "Fri, 28 Mar 2025 06:36:33 +0100")

Patrick Steinhardt <ps@pks.im> writes:

>> So we'll see a final reroll with the above changes and the topic
>> will finally be moving?  That's a great news.
>
> The topic can be merged as-is. The relevant MIMALLOC code only exists
> downstream in Git for Windows, so there is nothing that I can do about
> it in this series.
>
> Thanks all!

Thanks, both, for productive discussions.
Let me mark the topic for 'next'.


      parent reply	other threads:[~2025-03-29 23:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-01  0:45 What's cooking in git.git (Feb 2025, #09; Fri, 28) Junio C Hamano
2025-03-03 15:24 ` shejialuo
2025-03-03 17:03   ` Junio C Hamano
2025-03-04  6:27     ` Patrick Steinhardt
2025-03-04 12:25       ` shejialuo
2025-03-04 15:30       ` Junio C Hamano
2025-03-07 10:48     ` Karthik Nayak
2025-03-04  6:31 ` Patrick Steinhardt
2025-03-04  7:02   ` ps/reftable-sans-compat-util, was " Johannes Schindelin
2025-03-04  7:40     ` Johannes Schindelin
2025-03-04  9:46       ` Patrick Steinhardt
2025-03-04 10:06         ` Patrick Steinhardt
2025-03-26 16:57           ` Johannes Schindelin
2025-03-27 15:28             ` Junio C Hamano
2025-03-28  5:36               ` Patrick Steinhardt
2025-03-28 15:31                 ` Johannes Schindelin
2025-03-30  0:56                   ` Junio C Hamano
2025-03-29 23:56                 ` Junio C Hamano [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=xmqqplhzbdc2.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --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 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.