From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Glen Choo <chooglen@google.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: gc/zero-length-branch-config-fix (was Re: What's cooking in git.git (Jun 2022, #01; Wed, 1))
Date: Thu, 02 Jun 2022 10:37:39 +0200 [thread overview]
Message-ID: <220602.86mtevzchb.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <kl6lfskneugf.fsf@chooglen-macbookpro.roam.corp.google.com>
On Wed, Jun 01 2022, Glen Choo wrote:
> Junio C Hamano <gitster@pobox.com> 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@gmail.com>
>
> 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@chooglen-macbookpro.roam.corp.google.com
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.
next prev parent reply other threads:[~2022-06-02 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 0:55 What's cooking in git.git (Jun 2022, #01; Wed, 1) Junio C Hamano
2022-06-02 1:16 ` gc/zero-length-branch-config-fix (was Re: What's cooking in git.git (Jun 2022, #01; Wed, 1)) Glen Choo
2022-06-02 8:37 ` Ævar Arnfjörð Bjarmason [this message]
2022-06-02 12:13 ` ab/env-array (was: " Ævar Arnfjörð Bjarmason
2022-06-02 12:25 ` What's cooking in git.git (Jun 2022, #01; Wed, 1) Derrick Stolee
2022-06-02 14:07 ` Jeff Hostetler
2022-06-02 14:46 ` ab/bug-if-bug (was: What's cooking in git.git (Jun 2022, #01; Wed, 1)) Ævar Arnfjörð Bjarmason
2022-06-02 14:47 ` ab/hooks-regression-fix " Ævar Arnfjörð Bjarmason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=220602.86mtevzchb.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).