Re: [PATCH 3/4] reftable/stack: fix zero-sized allocation when there are no readers

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 21, 2024, 17:57 UTC
Message-ID: <xmqqmsgoc42a.fsf@gitster.g>
In-Reply-To: <xmqq34ihc4zt.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

>>  reftable/stack.c | 44 +++++++++++++++++++++++---------------------
>>  1 file changed, 23 insertions(+), 21 deletions(-)
>
> This somehow did not cleanly apply, so I whiggled it in manually.

That is because I usually ignore author-supplied base, and this time I used the tip of ps/reftable-alloc-failures topic, which brings all the text these four patches touch, in my initial attempt.

Applying these on the author-supplied base (ff795a5c5e) yields the same tree as the result of merging my manual application of these four patches to ps/reftable-alloc-failures into the same base.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.