git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (May 2022, #01; Mon, 2)

From
Junio C Hamano <gitster@pobox.com>
Date
May 5, 2022, 19:33 UTC
Message-ID
<xmqqh763dbay.fsf@gitster.g>
In-Reply-To
<CABPp-BF9ftVVp7-ZZuhak456x12-H941Nj4qV7gNf71rrugGhQ@mail.gmail.com>
Elijah Newren <newren@gmail.com> writes:
Show 27 quoted lines
> On Thu, May 5, 2022 at 9:15 AM Elijah Newren <newren@gmail.com> wrote:
>>
>> On Thu, May 5, 2022 at 8:56 AM Junio C Hamano <gitster@pobox.com> wrote:
>> >
> [...]
>> > I vaguely recall there were folks who didn't like the change of
>> > default the last time you brought this topic up.  Convincing them is
>> > not my job---it is yours.  Mine has been to help prepare the code
>> > ready for public consumption when that happens.
>>
>> That's a surprise to me; I don't remember anyone bringing that up,
>> ever.  Did I somehow miss it??  I'd be happy to talk to anyone and
>> hear their concerns if they do hold such an opinion.  Over the last
>> year or so both Stolee and Victoria have suggested such a change or
>> said they wondered why I didn't include such a change with other
>> sparse-checkout changes we were making, and I mentioned a few times I
>> thought it'd be a good future plan and finally submitted it.  To the
>> best of my memory, no one ever offered a counter opinion.
>>
>> Are you perhaps mixing this up with the case where people brought up
>> concerns with suggested tab-completion changes?  That's the only other
>> related series recently where folks brought up concerns with suggested
>> changes.
>
> So, I did a few searches through the list history for anyone that may
> have commented on cone mode as default.  The only comments I can find
> are Stolee, Victoria, Lessley, and I being in favor.

OK, so I misremembered. Let's hope that the list subscriber base is wide enough and those who will be affected are all in favor, and see how the reception by those who are not on the list goes.

Hopefully some organizations may have a canary channel for their users to try out something based on 'next', and we will hear from them, either positive or negative, about their experience.

Previous: Elijah NewrenNext: Johannes Schindelin
Message 9 of 12 in “What's cooking in git.git (May 2022, #01; Mon, 2)”
  1. Junio C HamanoMay 2, 2022
  2. Derrick StoleeMay 3, 2022
  3. Junio C HamanoMay 4, 2022
  4. Elijah NewrenMay 5, 2022
  5. Derrick StoleeMay 5, 2022
  6. Junio C HamanoMay 5, 2022
  7. Elijah NewrenMay 5, 2022
  8. Elijah NewrenMay 5, 2022
  9. Junio C HamanoMay 5, 2022
  10. cone mode as default for sparse-checkout?, was Re: What's cooking in git.git (May 2022, #01; Mon, 2)Johannes Schindelin, May 21, 2022
  11. brian m. carlsonMay 4, 2022
  12. Junio C HamanoMay 5, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.