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

ds/sparse-checkout-clean (was: What's cooking in git.git (Sep 2025, #10; Thu, 25))

From
Derrick Stolee <stolee@gmail.com>
Date
Sep 26, 2025, 13:42 UTC
Message-ID
<3537e220-44b6-4e37-a568-cef34a2fddfd@gmail.com>
In-Reply-To
<xmqqbjmydw5i.fsf@gitster.g>
On 9/25/2025 6:06 PM, Junio C Hamano wrote:
Show 16 quoted lines
> * ds/sparse-checkout-clean (2025-09-12) 7 commits
>   (merged to 'next' on 2025-09-25 at 00b296f153)
>  + t: expand tests around sparse merges and clean
>  + sparse-index: point users to new 'clean' action
>  + sparse-checkout: add --verbose option to 'clean'
>  + dir: add generic "walk all files" helper
>  + sparse-checkout: match some 'clean' behavior
>  + sparse-checkout: add basics of 'clean' command
>  + sparse-checkout: remove use of the_repository
> 
>  "git sparse-checkout" subcommand learned a new "clean" action to
>  prune otherwise unused working-tree files that are outside the
>  areas of interest.
> 
>  Will merge to 'master'.
>  source: <pull.1941.v3.git.1757673011.gitgitgadget@gmail.com>
 
I should have checked here first, but I pinged the patch series
to see if Elijah wanted to give another round of review following
his careful review of v2. If there is minor feedback, then maybe
I can forward-fix on top of this branch.

Thanks, -Stolee

Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 4 in “What's cooking in git.git (Sep 2025, #10; Thu, 25)”
  1. Junio C HamanoSep 25, 2025
  2. ds/sparse-checkout-clean (was: What's cooking in git.git (Sep 2025, #10; Thu, 25))Derrick Stolee, Sep 26, 2025
  3. Junio C HamanoOct 8, 2025
  4. Kristoffer HaugsbakkSep 29, 2025

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.