From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Elijah Newren <newren@gmail.com>
Subject: Re: What's cooking in git.git (Sep 2021, #02; Wed, 8)
Date: Wed, 8 Sep 2021 17:57:45 -0400 [thread overview]
Message-ID: <d6721839-114a-3309-25aa-1926fa198bf7@gmail.com> (raw)
In-Reply-To: <xmqqsfyf5b74.fsf@gitster.g>
On 9/8/2021 11:38 AM, Junio C Hamano wrote:> * ds/sparse-index-ignored-files (2021-09-07) 10 commits
> - sparse-checkout: clear tracked sparse dirs
> - sparse-index: add SPARSE_INDEX_MEMORY_ONLY flag
> - attr: be careful about sparse directories
> - sparse-checkout: create helper methods
> - sparse-index: use WRITE_TREE_MISSING_OK
> - sparse-index: silently return when cache tree fails
> - unpack-trees: fix nested sparse-dir search
> - sparse-index: silently return when not using cone-mode patterns
> - t7519: rewrite sparse index test
> - Merge branch 'ds/add-with-sparse-index' into ds/sparse-index-ignored-files
> (this branch is used by sg/test-split-index-fix.)
>
> In cone mode, the sparse-index codepath learned to remove ignored
> files (like build artifacts) outside the sparse cone, allowing the
> entire directory outside the sparse cone to be removed, which is
> especially useful when the sparse patterns change.
>
> Will merge to 'next'?
I think this one is ready to go. Elijah chimed in on the latest
version, too.
This also means that perhaps we could start tracking the sparse
index integrations with merge, rebase, cherry-pick, and revert [1]?
This series has also had quite a bit of review, but the latest
version has not had an ack.
[1] https://lore.kernel.org/git/pull.1019.v3.git.1631100241.gitgitgadget@gmail.com
I also plan to send a new version of the --sparse RFC [2], which
is based on [1]. I don't want to get too far ahead of what the
community has capacity to review.
[2] https://lore.kernel.org/git/pull.1018.git.1629842085.gitgitgadget@gmail.com/
Thanks,
-Stolee
next prev parent reply other threads:[~2021-09-08 21:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 15:38 What's cooking in git.git (Sep 2021, #02; Wed, 8) Junio C Hamano
2021-09-08 16:24 ` Taylor Blau
2021-09-08 19:23 ` Junio C Hamano
2021-09-09 1:02 ` Taylor Blau
2021-09-08 21:27 ` Jeff King
2021-09-08 16:55 ` Azeem Bande-Ali
2021-09-08 19:20 ` Junio C Hamano
2021-09-08 17:50 ` Philippe Blain
2021-09-08 21:57 ` Derrick Stolee [this message]
2021-09-09 14:23 ` Elijah Newren
2021-09-09 2:59 ` Ramsay Jones
2021-09-09 17:45 ` Junio C Hamano
2021-09-09 11:03 ` js/scalar, was " Johannes Schindelin
2021-09-10 8:52 ` Junio C Hamano
2021-09-09 11:05 ` rs/range-diff-avoid-segfault-with-I, " Johannes Schindelin
2021-09-09 11:08 ` js/retire-preserve-merges, " Johannes Schindelin
2021-09-10 5:00 ` Junio C Hamano
2021-09-09 11:08 ` mr/bisect-in-c-4, " Johannes Schindelin
2021-09-10 5:07 ` Junio C Hamano
2021-09-10 9:33 ` Johannes Schindelin
2021-09-09 11:13 ` lh/systemd-timers, " Johannes Schindelin
2021-09-09 11:15 ` ar/submodule-add-more, " Johannes Schindelin
2021-09-10 5:30 ` Junio C Hamano
2021-09-09 11:18 ` Ævar Arnfjörð Bjarmason
2021-09-09 14:12 ` Elijah Newren
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=d6721839-114a-3309-25aa-1926fa198bf7@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.