From: Patrick Steinhardt <ps@pks.im>
To: git@vger.kernel.org
Cc: Johannes.Schindelin@gmx.de, karthik.188@gmail.com,
sandals@crustytoothpaste.net
Subject: Re: [PATCH v4] refs/reftable: fix uninitialized memory access of `max_index`
Date: Mon, 27 Jan 2025 11:19:23 +0100 [thread overview]
Message-ID: <Z5ddq3DE071XLzEg@pks.im> (raw)
In-Reply-To: <b7e3dd3cc870024f0e80dad26c5a7a96483c6cf4.1737970803.git.ps@pks.im>
On Mon, Jan 27, 2025 at 10:44:08AM +0100, Patrick Steinhardt wrote:
> Karthik is out of office this week, so I'm taking over this series for
> him to ensure that it lands soonish. The only change compared to v3 is
> an adapted commit message based on my own feedback.
Ugh, sorry, forgot to set the In-reply-to header. This was meant as a
reply to [1].
Patrick
[1]: <CAOLa=ZR=Hz+LU0n-uC2dpk8_sLqAyaxO0NswJH8bP_kEdDdbUQ@mail.gmail.com>
next prev parent reply other threads:[~2025-01-27 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 9:44 [PATCH v4] refs/reftable: fix uninitialized memory access of `max_index` Patrick Steinhardt
2025-01-27 10:19 ` Patrick Steinhardt [this message]
2025-01-27 16:22 ` 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=Z5ddq3DE071XLzEg@pks.im \
--to=ps@pks.im \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=sandals@crustytoothpaste.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 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).