Re: [PATCH v5 0/3] completion: sparse-checkout updates

From: Lessley Dennington <lessleydennington@gmail.com>
Date: Feb 4, 2022, 02:43 UTC
Message-ID: <cb6f65b5-4e02-08af-bea6-141fb6227927@gmail.com>
In-Reply-To: <eb442213-d369-fdcd-c3a3-05239bccb5bf@gmail.com>

On 2/3/22 3:59 PM, Lessley Dennington wrote:

Show 36 quoted lines

> 
> 
> On 2/3/22 3:28 PM, Junio C Hamano wrote:
>> Lessley Dennington <lessleydennington@gmail.com> writes:
>>
>>> On 2/3/22 1:48 PM, Junio C Hamano wrote:
>>>> "Lessley Dennington via GitGitGadget" <gitgitgadget@gmail.com>
>>>> writes:
>>>>
>>>>> This series is based on en/sparse-checkout-set.
>>>> This has been a very helpful note, but after the topic was merged to
>>>> 'master' on Jan 3rd, it has become a tad stale.  Let me apply the
>>>> topic directly on v2.35.0 instead.
>>>> Thanks.
>>>
>>> Thank you for the heads up! I will remove from future versions.
>>
>> No problem.
>>
>> FWIW, the tip of 'seen' seems to be failing the CI; I haven't looked
>> into the cause of the breakage.
>>
>>    https://github.com/git/git/actions/runs/1792151138
>>
>> There is another CI job running on 'seen', whose only difference from
>> the above version is that this topic has been temporarily ejected:
>>
>>    https://github.com/git/git/actions/runs/1792296432
>>
>> We'll see if that fails the same way (in which this topic may not
>> have anything to do with the breakage) or if it passes.
>>
>> Thanks.
> 
> I just merged seen locally and was able to repro the failure. I will
> submit a fix ASAP.

GitGitGadget CI has passed with the fix, but it is not responding to the /submit command. As a heads up, fix may not be submitted until folks who are a bit more knowledgeable about GGG than I are available to help troubleshoot.