Re: gc/zero-length-branch-config-fix (was Re: What's cooking in git.git (Jun 2022, #01; Wed, 1))

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jun 01 2022, Glen Choo wrote:

> Junio C Hamano <gitster@xxxxxxxxx> writes:
>
>> * gc/zero-length-branch-config-fix (2022-06-01) 2 commits
>>  - remote.c: reject 0-length branch names
>>  - remote.c: don't BUG() on 0-length branch names
>>
>>  A misconfigured 'branch..remote' led to a bug in configuration
>>  parsing.
>>
>>  Will merge to 'next'?
>>  source: <pull.1273.git.git.1654038754.gitgitgadget@xxxxxxxxx>
>
> I'm happy to see this go to 'next' if Ævar doesn't have any lingering
> concerns over the commit message [1].
>
> [1] https://lore.kernel.org/git/kl6lilpke31e.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I'm happy to have it advance to "next" as-is. I just had a question
about if we thought this config existed in the wild, but that & the
answer can just live in the ML archive. Thanks.




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux