From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Patrick Steinhardt <ps@pks.im>, 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: Thu, 27 Mar 2025 08:28:34 -0700 [thread overview]
Message-ID: <xmqq34eyijbx.fsf@gitster.g> (raw)
In-Reply-To: <9cd879ed-5366-a7bf-f440-e35222a733d2@gmx.de> (Johannes Schindelin's message of "Wed, 26 Mar 2025 17:57:19 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> Below patch addresses the issue.
>>
>> Patrick
>>
>> diff --git a/compat/posix.h b/compat/posix.h
>> index b484029f751..5ad3539d55b 100644
>> --- a/compat/posix.h
>> +++ b/compat/posix.h
>> @@ -176,6 +176,16 @@ typedef unsigned long uintptr_t;
>> #define _ALL_SOURCE 1
>> #endif
>>
>> +#ifdef USE_MIMALLOC
>> +#include "mimalloc.h"
>> +#define malloc mi_malloc
>> +#define calloc mi_calloc
>> +#define realloc mi_realloc
>> +#define free mi_free
>> +#define strdup mi_strdup
>> +#define strndup mi_strndup
>> +#endif
>> +
>> #ifdef MKDIR_WO_TRAILING_SLASH
>> #define mkdir(a,b) compat_mkdir_wo_trailing_slash((a),(b))
>> int compat_mkdir_wo_trailing_slash(const char*, mode_t);
>> diff --git a/git-compat-util.h b/git-compat-util.h
>> index 8d2acf86670..a102a365592 100644
>> --- a/git-compat-util.h
>> +++ b/git-compat-util.h
>> @@ -226,16 +226,6 @@ static inline const char *precompose_string_if_needed(const char *in)
>> # include <sys/sysinfo.h>
>> #endif
>>
>> -#ifdef USE_MIMALLOC
>> -#include "mimalloc.h"
>> -#define malloc mi_malloc
>> -#define calloc mi_calloc
>> -#define realloc mi_realloc
>> -#define free mi_free
>> -#define strdup mi_strdup
>> -#define strndup mi_strndup
>> -#endif
>> -
>> #ifndef PATH_SEP
>> #define PATH_SEP ':'
>> #endif
>
> I integrated this into Git for Windows' `shears/seen` branch (i.e. the
> continuously-rebased Git for Windows patches on top of the `seen` branch),
> and for the first time in weeks, it passed the CI build:
> https://github.com/git-for-windows/git/actions/runs/14087673643
Thanks.
So we'll see a final reroll with the above changes and the topic
will finally be moving? That's a great news.
next prev parent reply other threads:[~2025-03-27 15:28 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 [this message]
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
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=xmqq34eyijbx.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.