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, 15:56 UTC
Message-ID
<xmqqmtfwezx5.fsf@gitster.g>
In-Reply-To
<CABPp-BHDKRX4sW_Jjqw5j7Voas0X_xkFZgg5Jqk0TkNZOd7k1g@mail.gmail.com>
Elijah Newren <newren@gmail.com> writes:
> 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.

Correct. The above is all assuming that "cone is the future" is what is shared by the population that depends on sparse-checkout. I do not have strong opinions to declare that, but to help the topic move forward, I was giving reviews under the condition, i.e. "If there is such a concensus, here are the things in your current iteration that would need to be addressed".

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.

Previous: Derrick StoleeNext: Elijah Newren
Message 6 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.