git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] unpack-trees: fix sparse directory recursion check

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 2, 2022, 16:57 UTC
Message-ID
<xmqqr10t90jb.fsf@gitster.g>
In-Reply-To
<8dea9ffe-d03b-f838-6cc5-db0de5024d9f@github.com>
Derrick Stolee <derrickstolee@github.com> writes:
Show 9 quoted lines
> Could it also happen if we are going from a commit without that
> sparse directory and then to a commit with that sparse directory? I
> think that would be a more common case, but I was unable to
> manipulate the test repo in t1092 to trigger this bug in the existing
> test cases.
>
> This makes me think that this bug _is_ extremely rare, so we don't
> need to rush this into a 2.37.4 or anything. It would be good to
> bring it into 2.38.0-rc0, though.

When the "test" part of the patch is applied directly on top of the vd/sparse-reset-checkout-fixes topic without its "fix" part, the newly added test fails, and with the "fix" part applied, everything goes peachy. I think applying it on top of the topic as a fix to it would be the most sensible. Any motivated distro packager can grab the topic and merge to their long-term maintenance track that way more easily.

Thanks all.
Previous: Derrick StoleeNext: Shaoxuan Yuan
Message 4 of 5 in “unpack-trees: fix sparse directory recursion check”
  1. unpack-trees: fix sparse directory recursion checkVictoria Dye via GitGitGadget, Sep 1, 2022
  2. Johannes SchindelinSep 2, 2022
  3. Derrick StoleeSep 2, 2022
  4. Junio C HamanoSep 2, 2022
  5. Shaoxuan YuanSep 2, 2022

Read the whole thread, see it on lore, or plain text.

$ 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.