From: Junio C Hamano <gitster@pobox•com>
To: Jonathan Tan <jonathantanmy@google•com>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Nov 2024, #04; Fri, 8)
Date: Tue, 12 Nov 2024 10:19:22 +0900 [thread overview]
Message-ID: <xmqq8qtp8d0l.fsf@gitster.g> (raw)
In-Reply-To: <xmqqcyj18dkx.fsf@gitster.g> (Junio C. Hamano's message of "Tue, 12 Nov 2024 10:07:10 +0900")
Junio C Hamano <gitster@pobox•com> writes:
>> The fixup in your source tree looks good (verified at
>> https://github.com/jonathantanmy/git/actions/runs/11787543288).
>
> Thanks. Will squashing it in all it takes or does it require more
> (like log message updates, perhaps)?
It seems that that one more "free()" can be squashed in without
anything else. So I'll do that and merge the result to 'next'.
Thanks.
prev parent reply other threads:[~2024-11-12 1:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 8:03 What's cooking in git.git (Nov 2024, #04; Fri, 8) Junio C Hamano
2024-11-11 23:53 ` Jonathan Tan
2024-11-12 1:07 ` Junio C Hamano
2024-11-12 1:19 ` 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=xmqq8qtp8d0l.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jonathantanmy@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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