From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: malloc: *** error for object 0x1: pointer being freed was not allocated on MacOS with git 2.47.0
Date: Mon, 18 Nov 2024 21:42:03 +0900 [thread overview]
Message-ID: <xmqqjzd0k92c.fsf@gitster.g> (raw)
In-Reply-To: <Zzr4cgk_5MJNcHm1@pks.im> (Patrick Steinhardt's message of "Mon, 18 Nov 2024 09:19:04 +0100")
Patrick Steinhardt <ps@pks.im> writes:
>> ds/line-log-asan-fix # 1 (2024-10-10)
>> jk/fsmonitor-event-listener-race-fix # 2 (2024-10-15)
>> ps/maintenance-start-crash-fix # 1 (2024-10-18)
>
> Other candidates that fix regressions:
>
> jk/fetch-prefetch-double-free-fix
> tb/multi-pack-reuse-dupfix
Neither of these has hit 'master' yet.
> pb/clar-build-fix
Not all that urgent (it is not end-user facing).
> ps/upgrade-clar
> wm/shortlog-hash
Unfortuately, these were both based not on 'maint' but on 'master',
and cannot ever be merged down to 'maint'. The last topic may
deserve to be cherry-picked to 'maint' when the time comes.
Right now I have these lined up for 'maint'
ds/line-log-asan-fix
jk/fsmonitor-event-listener-race-fix
ps/maintenance-start-crash-fix
ps/cache-tree-w-broken-index-entry
db/submodule-fetch-with-remote-name-fix
Thanks.
next prev parent reply other threads:[~2024-11-18 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 9:40 malloc: *** error for object 0x1: pointer being freed was not allocated on MacOS with git 2.47.0 Attila Kerekes
2024-11-15 16:34 ` René Scharfe
2024-11-15 17:23 ` Junio C Hamano
2024-11-18 8:19 ` Patrick Steinhardt
2024-11-18 12:42 ` Junio C Hamano [this message]
2024-11-18 13:07 ` Patrick Steinhardt
2024-11-18 23:51 ` Junio C Hamano
2024-11-18 19:28 ` Philippe Blain
2024-11-19 0:33 ` 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=xmqqjzd0k92c.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