From: Junio C Hamano <gitster@pobox.com>
To: Victoria Dye <vdye@github.com>
Cc: git@vger.kernel.org
Subject: Re: vd/sparse-reset
Date: Mon, 29 Nov 2021 12:48:44 -0800 [thread overview]
Message-ID: <xmqqo8626637.fsf@gitster.g> (raw)
In-Reply-To: <dc976377-6c2d-2d82-a128-a4316c3bcee2@github.com> (Victoria Dye's message of "Mon, 29 Nov 2021 10:56:17 -0500")
Victoria Dye <vdye@github.com> writes:
> Junio C Hamano wrote:
>> * vd/sparse-reset (2021-10-27) 8 commits
>> - unpack-trees: improve performance of next_cache_entry
>> - reset: make --mixed sparse-aware
>> - reset: make sparse-aware (except --mixed)
>> - reset: integrate with sparse index
>> - reset: expand test coverage for sparse checkouts
>> - sparse-index: update command for expand/collapse test
>> - reset: preserve skip-worktree bit in mixed reset
>> - reset: rename is_missing to !is_in_reset_tree
>> (this branch is used by ds/fetch-pull-with-sparse-index and ld/sparse-diff-blame.)
>>
>> Various operating modes of "git reset" have been made to work
>> better with the sparse index.
>>
>> Will merge to 'next'.
>>
>
> I submitted one last change to this series in response to Elijah's review
> (threads: [1], [2]). I don't think there's any other outstanding feedback to
> address, so that version (V6) should be the one to merge to 'next' (unless
> any issues arise from the update itself). Thanks!
>
> [1] https://lore.kernel.org/git/c97e4252-b17a-c8c1-3bde-cbfe22a6e4d5@github.com/
>
> [2] https://lore.kernel.org/git/b3f33d40-d418-f285-4a32-1db7a2c4c465@github.com/
It is always a pain to have a topic that is still being rerolled to
be depended upon by other topics. Once we merge this to 'next', it
would hopefully become easier to manage.
Thanks.
next prev parent reply other threads:[~2021-11-29 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 5:56 What's cooking in git.git (Nov 2021, #06; Wed, 24) Junio C Hamano
2021-11-25 13:11 ` Philip Oakley
2021-11-26 13:11 ` bc/require-c99 + jc/c99-var-decl-in-for-loop (was: What's cooking in git.git (Nov 2021, #06; Wed, 24)) Ævar Arnfjörð Bjarmason
2021-11-29 2:29 ` bc/require-c99 + jc/c99-var-decl-in-for-loop Junio C Hamano
2021-11-29 15:56 ` vd/sparse-reset (Was: Re: What's cooking in git.git (Nov 2021, #06; Wed, 24)) Victoria Dye
2021-11-29 20:48 ` Junio C Hamano [this message]
2021-11-29 22:30 ` Submodules UX overhaul update (was: " Emily Shaffer
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqo8626637.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=vdye@github.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).