Leo Razoumov writes:
> On Sun, Jul 9, 2017 at 5:57 AM, Jeff King wrote:
>> On Sun, Jul 09, 2017 at 05:28:34AM -0400, Jeff King wrote:
>>
>>> On Sat, Jul 08, 2017 at 03:13:04PM -0400, Leo Razoumov wrote:
>>>
>>> > When I updated from git-2.10.2 to git-2.13.2
On Sun, Jul 9, 2017 at 5:57 AM, Jeff King wrote:
> On Sun, Jul 09, 2017 at 05:28:34AM -0400, Jeff King wrote:
>
>> On Sat, Jul 08, 2017 at 03:13:04PM -0400, Leo Razoumov wrote:
>>
>> > When I updated from git-2.10.2 to git-2.13.2 my 'color.branch.local'
>> > config setting gets
On Sun, Jul 09, 2017 at 05:28:34AM -0400, Jeff King wrote:
> On Sat, Jul 08, 2017 at 03:13:04PM -0400, Leo Razoumov wrote:
>
> > When I updated from git-2.10.2 to git-2.13.2 my 'color.branch.local'
> > config setting gets ignored. Corresponding 'remote' or 'current'
> > settings are honored and
On Sat, Jul 08, 2017 at 03:13:04PM -0400, Leo Razoumov wrote:
> When I updated from git-2.10.2 to git-2.13.2 my 'color.branch.local'
> config setting gets ignored. Corresponding 'remote' or 'current'
> settings are honored and work as expected
Looks like this is a regression from the switch to
Hi Everyone,
When I updated from git-2.10.2 to git-2.13.2 my 'color.branch.local'
config setting gets ignored. Corresponding 'remote' or 'current'
settings are honored and work as expected
Relevant parts of my config file is:
[color "branch"]
current= reverse
local = red bold
5 matches
Mail list logo