Re: Mistakes in the stalled category?
- From
Derrick Stolee <stolee@gmail.com>
- Date
- Jan 18, 2022, 16:11 UTC
- Message-ID
- <0d6269b5-95ea-c2cd-6e5f-f10e874525d5@gmail.com>
- In-Reply-To
- <xmqqiluk4wo4.fsf@gitster.g>
On 1/15/2022 2:38 PM, Junio C Hamano wrote:
Show 28 quoted lines
> Junio C Hamano <gitster@pobox.com> writes: > >> Elijah Newren <newren@gmail.com> writes: >> >>>> [Stalled] >>>> >>>> * ds/sparse-checkout-requires-per-worktree-config (2021-12-21) 5 commits >> >> [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. > > The pushout of 'seen' I did after -rc1 last night included this > topic again; https://github.com/git/git/actions/runs/1700157728 > > The CI job triggered Leak Sanitizer in "git init" (the first thing > tests do is to prepare a test repository with working tree, so there > may be other new breakages, but we wouldn't know) and broke CI. > > This morning, just to test, I ejected this topic from 'seen' and > pushed it out; https://github.com/git/git/actions/runs/1702373554 > > As the only difference between these two runs is this topic, it may > be worth looking into locating and fixing new leaks introduced by > it.
Thanks for pointing this out. I will work to fix this leak in the next version. Feel free to eject it until the new version is available.
Thanks, -Stolee