From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2025, #09; Mon, 22)
Date: Tue, 23 Sep 2025 07:14:29 -0700 [thread overview]
Message-ID: <xmqq348dqmre.fsf@gitster.g> (raw)
In-Reply-To: <20250923031942.GA1484@coredump.intra.peff.net> (Jeff King's message of "Mon, 22 Sep 2025 23:19:42 -0400")
Jeff King <peff@peff.net> writes:
> On Mon, Sep 22, 2025 at 04:01:01PM -0700, Junio C Hamano wrote:
>
>> * jk/setup-revisions-freefix (2025-09-19) 6 commits
>> (merged to 'next' on 2025-09-22 at b178f27e6d)
>> + revision: retain argv NULL invariant in setup_revisions()
>> + treewide: pass strvecs around for setup_revisions_from_strvec()
>> + treewide: use setup_revisions_from_strvec() when we have a strvec
>> + revision: add wrapper to setup_revisions() from a strvec
>> + revision: manage memory ownership of argv in setup_revisions()
>> + stash: tell setup_revisions() to free our allocated strings
>>
>> There are double frees and leaks around setup_revisions() API used
>> in "git stash show", which has been fixed, and setup_revisions()
>> API gained a wrapper to make it more ergonomic when using it with
>> strvec-manged argc/argv pairs.
>>
>> Expecting a reroll to fix t3903
>> cf. <xmqq1pnywkwv.fsf@gitster.g>
>> source: <20250919223351.GA3906184@coredump.intra.peff.net>
>
> Hmm, I was surprised to see this merged to next, especially with the
> comment at the bottom here.
Yeah, I am surprised too ;-) Will fix.
Thanks.
next prev parent reply other threads:[~2025-09-23 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 23:01 What's cooking in git.git (Sep 2025, #09; Mon, 22) Junio C Hamano
2025-09-23 3:19 ` Jeff King
2025-09-23 14:14 ` Junio C Hamano [this message]
2025-09-23 7:42 ` Patrick Steinhardt
2025-09-23 14:34 ` Junio C Hamano
2025-09-24 6:44 ` SZEDER Gábor
2025-09-24 7:00 ` Patrick Steinhardt
2025-09-24 19:01 ` 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=xmqq348dqmre.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.