From: Derrick Stolee <stolee@gmail•com>
To: Elijah Newren <newren@gmail•com>, Junio C Hamano <gitster@pobox•com>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Sep 2025, #03; Mon, 8)
Date: Tue, 9 Sep 2025 15:35:06 -0400 [thread overview]
Message-ID: <e76a86b3-f913-49a9-a886-32d8d3baefb4@gmail.com> (raw)
In-Reply-To: <CABPp-BGxzRmkqdkpsVE=b9hQUsA9QO8iTNL=Wan1Vwatq5bMMQ@mail.gmail.com>
On 9/9/2025 2:58 AM, Elijah Newren wrote:
> On Mon, Sep 8, 2025 at 6:38 PM Junio C Hamano <gitster@pobox•com> wrote:
>
>> * ds/sparse-checkout-clean (2025-07-16) 7 commits
>> - sparse-checkout: make 'clean' clear more files
>> - 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
>>
>> "git sparse-checkout" subcommand learned a new "clean" action to
>> prune otherwise unused working-tree files that are outside the
>> areas of interest.
>>
>> Rebased not to depend on ac/deglobal-sparse-variables
>> Will merge to 'next'?
>> source: <pull.1941.v2.git.1752716054.gitgitgadget@gmail•com>
>
> No, please. Responses to review comments are still needed, as noted
> over at https://lore.kernel.org/git/c3c0fbef-f395-4972-8352-dd89af6799d5@gmail.com/
Indeed, I am delinquent with responses to those review
comments. I hope to have a v3 this week.
Thanks,
-Stolee
next prev parent reply other threads:[~2025-09-09 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 1:37 What's cooking in git.git (Sep 2025, #03; Mon, 8) Junio C Hamano
2025-09-09 6:58 ` Elijah Newren
2025-09-09 19:35 ` Derrick Stolee [this message]
2025-09-09 21:20 ` Junio C Hamano
2025-09-10 7:42 ` Kristoffer Haugsbakk
2025-09-10 21:37 ` Junio C Hamano
2025-09-10 21:44 ` Kristoffer Haugsbakk
2025-09-10 15:32 ` Phillip Wood
2025-09-10 21:38 ` Junio C Hamano
2025-09-10 15:54 ` Jeff King
2025-09-10 21:42 ` 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=e76a86b3-f913-49a9-a886-32d8d3baefb4@gmail.com \
--to=stolee@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=newren@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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