From: Derrick Stolee <derrickstolee@github.com>
To: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Elijah Newren <newren@gmail.com>,
Victoria Dye <vdye@github.com>
Subject: Re: What's cooking in git.git (May 2022, #01; Mon, 2)
Date: Tue, 3 May 2022 17:19:57 -0400 [thread overview]
Message-ID: <0facc01f-ee36-333a-eb25-9c98d616700e@github.com> (raw)
In-Reply-To: <xmqqilqnvacd.fsf@gitster.g>
On 5/2/2022 6:27 PM, Junio C Hamano wrote:
> * ds/sparse-colon-path (2022-04-26) 5 commits
> - rev-parse: integrate with sparse index
> - object-name: diagnose trees in index properly
> - object-name: reject trees found in the index
> - show: integrate with the sparse index
> - t1092: add compatibility tests for 'git show'
>
> "git show :<path>" learned to work better with the sparse-index
> feature.
>
> Will merge to 'next'?
> source: <pull.1207.v2.git.1651005800.gitgitgadget@gmail.com>
I think this is stable and ready to go. Unless anyone else wanted to
take a stab at reviewing it. I think we've got good eyes on it already.
> * en/sparse-cone-becomes-default (2022-04-21) 9 commits
> - Documentation: some sparsity wording clarifications
> - git-sparse-checkout.txt: mark non-cone mode as deprecated
> - git-sparse-checkout.txt: flesh out pattern set sections a bit
> - git-sparse-checkout.txt: add a new EXAMPLES section
> - git-sparse-checkout.txt: shuffle some sections and mark as internal
> - git-sparse-checkout.txt: update docs for deprecation of 'init'
> - git-sparse-checkout.txt: wording updates for the cone mode default
> - sparse-checkout: make --cone the default
> - tests: stop assuming --no-cone is the default mode for sparse-checkout
>
> Deprecate non-cone mode of the sparse-checkout feature.
>
> Will merge to 'next'?
> source: <pull.1148.v3.git.1650594746.gitgitgadget@gmail.com>
This has been quite stable and I'd like to see it merge early in the
release cycle in case that catches anything during local testing.
Thanks,
-Stolee
next prev parent reply other threads:[~2022-05-03 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 22:27 What's cooking in git.git (May 2022, #01; Mon, 2) Junio C Hamano
2022-05-03 21:19 ` Derrick Stolee [this message]
2022-05-04 16:18 ` Junio C Hamano
2022-05-05 15:04 ` Elijah Newren
2022-05-05 15:13 ` Derrick Stolee
2022-05-05 15:56 ` Junio C Hamano
2022-05-05 16:15 ` Elijah Newren
2022-05-05 18:53 ` Elijah Newren
2022-05-05 19:33 ` Junio C Hamano
2022-05-21 21:48 ` cone mode as default for sparse-checkout?, was " Johannes Schindelin
2022-05-04 21:56 ` brian m. carlson
2022-05-05 0:03 ` 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=0facc01f-ee36-333a-eb25-9c98d616700e@github.com \
--to=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--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.
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 NNTP newsgroup(s).