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

Re: [PATCH 1/1] sparse-checkout: respect core.ignoreCase in cone mode

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 13, 2019, 19:05 UTC
Message-ID
<xmqqwob0jbba.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<7aeb1589-cc08-654f-1bc0-d48fec1c0729@gmail.com>
Derrick Stolee <stolee@gmail.com> writes:
> If you have a plan for that branch and the merge status of those
> commits, then I'm happy to re-target my PR against 'next' or
> an equivalent branch.

This change does not make much sense without the cone-mode topic, no?

Previous: Derrick StoleeNext: Derrick Stolee
Message 10 of 16 in “sparse-checkout: respect core.ignoreCase in cone mode”
  1. 0/1 sparse-checkout: respect core.ignoreCase in cone modeDerrick Stolee via GitGitGadget, Dec 9, 2019
  2. 1/1 sparse-checkout: respect core.ignoreCase in cone modeDerrick Stolee via GitGitGadget, Dec 9, 2019
  3. Junio C HamanoDec 11, 2019
  4. Derrick StoleeDec 11, 2019
  5. Junio C HamanoDec 11, 2019
  6. Derrick StoleeDec 11, 2019
  7. Junio C HamanoDec 11, 2019
  8. Derrick StoleeDec 12, 2019
  9. Derrick StoleeDec 12, 2019
  10. Junio C HamanoDec 13, 2019
  11. Derrick StoleeDec 13, 2019
  12. Junio C HamanoDec 13, 2019
  13. 0/1 sparse-checkout: respect core.ignoreCase in cone modeDerrick Stolee via GitGitGadget, Dec 13, 2019
  14. 1/1 sparse-checkout: respect core.ignoreCase in cone modeDerrick Stolee via GitGitGadget, Dec 13, 2019
  15. Junio C HamanoDec 13, 2019
  16. Ed MasteDec 18, 2019

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.