Re: What's cooking in git.git (Feb 2019, #02; Wed, 6)

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 12, 2019, 03:10 UTC
Message-ID: <xmqq8sylg0r7.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <CACUQV58vvDzhqRrtutZMDV_Kkz137oP6rLUODaniMekfGa5gyQ@mail.gmail.com>

Rafael Ascensão <rafa.almas@gmail.com> writes:

Show 11 quoted lines

> On Thu, Feb 7, 2019 at 7:28 AM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> * du/branch-show-current (2018-10-26) 1 commit - branch: introduce
>> --show-current display option
>>
>>  "git branch" learned a new subcommand "--show-current".
>>
>>  Will merge to 'next'.
>>
>
> Did something change? I may have missed it. Until last what's cooking, this was

Nothing. I just do not care about this Meh? topic too strongly either way.

Show 16 quoted lines

> marked with:
>
> On Tue, Feb 5, 2019 at 11:56 PM Junio C Hamano <gitster@pobox.com> wrote:
>>
>>  I am personally not yet quite convinced if this is worth pursuing.
>>
>
> I also suggested a different implementation which simplifies it and should
> remove some unreachable checks that can be seen in "Git Test Coverage Report
> (Wednesday, Feb. 6)"
> https://public-inbox.org/git/20181107225619.6683-1-rafa.almas@gmail.com/
>
> I was expecting Daniels to squash these changes into his patch or for it to be
> dropped in favor of something else. For example adding `--list-head` instead,
> as discussed in early versions of this patch.
> https://public-inbox.org/git/20181011223457.GB7131@rigel/

Good. Then I'll freeze that topic and expect you help Daniels to improve the patch further ;-)

Thanks.