From: Jeff King <peff@peff.net>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Subject: Re: [PATCH 0/2] small leak fix in format-patch
Date: Sun, 5 Jul 2026 20:01:40 -0400 [thread overview]
Message-ID: <20260706000140.GB2301945@coredump.intra.peff.net> (raw)
In-Reply-To: <CAOLa=ZRX9fGPdtUKXhmJF-zm_+F0zDuXSV+w02ZPEzqXY6n1Fw@mail.gmail.com>
On Sat, Jul 04, 2026 at 02:13:52PM -0700, Karthik Nayak wrote:
> Jeff King <peff@peff.net> writes:
>
> > This fixes a leak I found while discussing an unrelated leak in another
> > thread[1]. As a bonus, this fixes some minor recent breakage of
> > leak-reporting when running the test suite under prove. The patches can
> > be split into separate topics if we want.
>
> I think you meant to CC the other "Kaartic" :)
Yes, I figured that out about halfway through the discussion and hoped
nobody might notice. ;) Sorry to both of you for the confusion.
-Peff
prev parent reply other threads:[~2026-07-06 0:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 6:39 [PATCH 0/2] small leak fix in format-patch Jeff King
2026-06-30 6:41 ` [PATCH 1/2] t: move LSan errors from stdout to stderr Jeff King
2026-06-30 6:43 ` [PATCH 2/2] format-patch: fix leak of rev_info in prepare_bases() Jeff King
2026-06-30 10:26 ` Patrick Steinhardt
2026-07-01 8:13 ` Jeff King
2026-07-01 8:42 ` Patrick Steinhardt
2026-07-01 8:47 ` Jeff King
2026-07-01 9:01 ` Patrick Steinhardt
2026-07-02 8:58 ` Jeff King
2026-07-02 10:08 ` Patrick Steinhardt
2026-07-03 20:45 ` Junio C Hamano
2026-07-06 0:34 ` Jeff King
2026-07-06 5:57 ` Patrick Steinhardt
2026-07-04 21:13 ` [PATCH 0/2] small leak fix in format-patch Karthik Nayak
2026-07-06 0:01 ` Jeff King [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=20260706000140.GB2301945@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--cc=karthik.188@gmail.com \
--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