From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Patrick Steinhardt <ps@pks.im>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2024, #01; Mon, 3)
Date: Wed, 05 Jun 2024 09:30:00 -0700 [thread overview]
Message-ID: <xmqqle3juzcn.fsf@gitster.g> (raw)
In-Reply-To: <20240605083526.GB2345232@coredump.intra.peff.net> (Jeff King's message of "Wed, 5 Jun 2024 04:35:26 -0400")
Jeff King <peff@peff.net> writes:
> I do think it's the wrong fix in the long term, and we'd want a patch
> like this on top of the merge of jc/t1517-more and ps/no-writable-strings.
Oh, of course. The "other topics" restructure the cmd_main() to
have a single exit point where we can release resources centrally.
Thanks.
next prev parent reply other threads:[~2024-06-05 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 6:16 What's cooking in git.git (Jun 2024, #01; Mon, 3) Junio C Hamano
2024-06-04 8:06 ` Patrick Steinhardt
2024-06-04 8:07 ` Karthik Nayak
2024-06-04 18:31 ` Junio C Hamano
2024-06-04 8:52 ` Jeff King
2024-06-04 18:36 ` Junio C Hamano
2024-06-05 8:35 ` Jeff King
2024-06-05 16:30 ` Junio C Hamano [this message]
2024-06-04 8:59 ` Christian Couder
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=xmqqle3juzcn.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--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;
as well as URLs for NNTP newsgroup(s).