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

Re: Mistakes in the stalled category?

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 14, 2022, 23:49 UTC
Message-ID
<xmqqlezh98uj.fsf@gitster.g>
In-Reply-To
<CABPp-BFj8NyXG6cQPJeDE46eicbfnP=TgEirRZVcnMM+YNG7OQ@mail.gmail.com>
Elijah Newren <newren@gmail.com> writes:
Show 19 quoted lines
>> [Stalled]
>>
>> * ds/sparse-checkout-requires-per-worktree-config (2021-12-21) 5 commits
>>  . sparse-checkout: use repo_config_set_worktree_gently()
>>  . config: add repo_config_set_worktree_gently()
>>  . worktree: add upgrade_to_worktree_config()
>>  . config: make some helpers repo-aware
>>  . setup: use a repository when upgrading format
>>
>>  "git sparse-checkout" wants to work with per-worktree configration,
>>  but did not work well in a worktree attached to a bare repository.
>>  source: <pull.1101.v2.git.1640114048.gitgitgadget@gmail.com>
>
> It has been two weeks since the last submission and emails about this
> topic, so maybe you put this one in "stalled" intentionally.  (If so,
> and Stolee if this really is stalled, would you like me to try
> updating?  I know it has expanded quite a bit from the early simple
> fix you were trying to provide, but you've got most the code I think
> you need and some important fixes I wouldn't want to see dropped.)

[Stalled] being early in the report is primarily a way to remind us that an update is overdue.

<1db0f601-4769-15c0-cd58-ecddfa1fc9d5@gmail.com> is what prompted me to consider that I can put it on backburner and spend my time on other topics.

>> * pw/add-p-hunk-split-fix (2022-01-12) 2 commits

I think what happened was that the previous iteration of this was on 2021-12-20 and marked as "Expecting a reroll" for a few issues of the "What's cooking" report. And then I've moved it to [Stalled] section, but before I had a chance to issue another "What's cooking" report, an update came, and when I updated the list of commits, I forgot to move the topic out of the [Stalled] category.

>> * gc/fetch-negotiate-only-early-return (2022-01-12) 3 commits
Likewise, the previous round was on 2021-12-21.
Previous: Junio C HamanoNext: Junio C Hamano
Message 12 of 19 in “What's cooking in git.git (Jan 2022, #03; Thu, 13)”
  1. Junio C HamanoJan 14, 2022
  2. Junio C HamanoJan 14, 2022
  3. Elijah NewrenJan 14, 2022
  4. Junio C HamanoJan 14, 2022
  5. Elijah NewrenJan 14, 2022
  6. Junio C HamanoJan 14, 2022
  7. Junio C HamanoJan 14, 2022
  8. Ævar Arnfjörð BjarmasonJan 14, 2022
  9. Patrick SteinhardtJan 17, 2022
  10. Mistakes in the stalled category? (Was: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13))Elijah Newren, Jan 14, 2022
  11. Junio C HamanoJan 14, 2022
  12. Junio C HamanoJan 14, 2022
  13. Junio C HamanoJan 15, 2022
  14. Derrick StoleeJan 18, 2022
  15. en/present-despite-skipped & en/remerge-diff (Was: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13))Elijah Newren, Jan 14, 2022
  16. tb/midx-bitmap-corruption-fix (was: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13))Taylor Blau, Jan 14, 2022
  17. David AguilarJan 15, 2022
  18. Junio C HamanoJan 15, 2022
  19. David AguilarJan 16, 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.