git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derrick Stolee <derrickstolee@github.com>
To: Elijah Newren <newren@gmail.com>, Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>, Victoria Dye <vdye@github.com>
Subject: Re: What's cooking in git.git (May 2022, #01; Mon, 2)
Date: Thu, 5 May 2022 11:13:18 -0400	[thread overview]
Message-ID: <720e86b3-367d-ab83-d3ba-a05cdf9bf0c2@github.com> (raw)
In-Reply-To: <CABPp-BHDKRX4sW_Jjqw5j7Voas0X_xkFZgg5Jqk0TkNZOd7k1g@mail.gmail.com>

On 5/5/2022 11:04 AM, Elijah Newren wrote:
> On Wed, May 4, 2022 at 9:18 AM Junio C Hamano <gitster@pobox.com> wrote:
>>
>>>> * 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.
>>
>> This one I am not worried about stability all that much; I am more
>> worried about breaking those who do not believe in "cone is the
>> future" and managing their expectations.
> 
> What path forward would you like to see?
> 
> On v2 you said, "There are a few things that I found questionable, but
> they were mostly documentation issues".  You brought up several points
> in v2 where my wording in the Documentation was admittedly suboptimal,
> though I think I addressed all of those in v3.
> 
> I also brought up an alternative change for consideration in the cover
> letter, though you didn't comment on it and other reviewers, while
> okay with the alternative, seemed to agree with my proposed changes in
> the series over the alternative.
> 
> Also, it might be worth noting:
>   - sparse-checkout, the capability in Git since ~2010, remains
> unmodified by these changes
>   - sparse-checkout, the subcommand added a couple years ago, still
> supports all non-cone mode behaviors it did before
>   - the change here is that the sparse-checkout subcommand's default
> becomes cone mode, along with documentation updates

I think Junio's concerns are the same ones we have had that delayed
this switch from the start: we don't know who might be surprised by
this change.

We've given this enough time to collect opinions from interested
parties that watch the list, but we need the next level of feedback
at this point. That's why I'm advocating to merge this now and have
a long time before the release to gather feedback.

Thanks,
-Stolee

  reply	other threads:[~2022-05-05 15:13 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
2022-05-04 16:18   ` Junio C Hamano
2022-05-05 15:04     ` Elijah Newren
2022-05-05 15:13       ` Derrick Stolee [this message]
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=720e86b3-367d-ab83-d3ba-a05cdf9bf0c2@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).