Re: Windows > git.exe > the result of "git branch" does not always highlight the current branch

From: Hari Lubovac <hlubovac@gmail.com>
Date: Apr 9, 2018, 20:06 UTC
Message-ID: <CAFLu24kTRrAq3cOH5H1=nBT94p7uFSsaYJsUC-wN1brPFHk3mQ@mail.gmail.com>
In-Reply-To: <CAGZ79kZ6xWijnZZpcogVm_JCX3nGMzN8ebKyh1vYygNc_dqGFw@mail.gmail.com>

I don't know which party compiled it. I'm pretty sure I downloaded the installer from https://git-scm.com/downloads, although it might have come shipped with Microsoft Visual Studio, which I use.

I forgot this detail earlier:

git --version git version 2.16.1.windows.2

I'm a little behind; maybe I should upgrade.

I just reported the same here: https://github.com/git-for-windows/git/issues/1623

On Mon, Apr 9, 2018 at 12:32 PM, Stefan Beller <sbeller@google.com> wrote:

Show 31 quoted lines

> Hi Hari,
>
> thanks for reporting a bug!
>
> On Mon, Apr 9, 2018 at 12:26 PM, Hari Lubovac <hlubovac@gmail.com> wrote:
>> It appears to be just a reporting issue. Probably not a big deal, but
>> I thought I should report this, if it hasn't been noticed: when a
>> branch is switched to by being named with non-original
>> character-casing, then it's not clear which branch is current.
>>
>> Example:
>>
>> C:\repo>git branch
>> * bar
>>   foo
>>
>> C:\repo>git checkout Bar
>> Switched to branch 'Bar'
>>
>> C:\repo>git branch
>>   bar
>>   foo
>
> Is this Git compiled under Windows or
> Git-for-Windows as distributed by Johannes?
>
> AFAICT Git-for-Windows prefers to have a bug on github
> https://github.com/git-for-windows/git/issues/new
>
> Thanks,
> Stefan