Re: [PATCH v10 19/20] branch: use ref-filter printing APIs
- From
Jacob Keller <jacob.keller@gmail.com>
- Date
- Jan 15, 2017, 05:51 UTC
- Message-ID
- <CA+P7+xoN12HqaVnYfESrf3-1ZSWkxAz9K+7rRi2gPpGPNSYmHQ@mail.gmail.com>
- In-Reply-To
- <CAOLa=ZQR9ksPtRw_9FneN26Mjq1TVYx7o=YOM4cDNgrDbuQtXg@mail.gmail.com>
On Sat, Jan 14, 2017 at 2:01 AM, Karthik Nayak <karthik.188@gmail.com> wrote:
Show 36 quoted lines
> Hello,
>
> On Thu, Jan 12, 2017 at 5:17 AM, Jacob Keller <jacob.keller@gmail.com> wrote:
>> On Tue, Jan 10, 2017 at 12:49 AM, Karthik Nayak <karthik.188@gmail.com> wrote:
>>> diff --git a/builtin/branch.c b/builtin/branch.c
>>> index 34cd61cd9..f293ee5b0 100644
>>> --- a/builtin/branch.c
>>> +++ b/builtin/branch.c
>>> @@ -37,11 +37,11 @@ static unsigned char head_sha1[20];
>>> static int branch_use_color = -1;
>>> static char branch_colors[][COLOR_MAXLEN] = {
>>> GIT_COLOR_RESET,
>>> - GIT_COLOR_NORMAL, /* PLAIN */
>>> - GIT_COLOR_RED, /* REMOTE */
>>> - GIT_COLOR_NORMAL, /* LOCAL */
>>> - GIT_COLOR_GREEN, /* CURRENT */
>>> - GIT_COLOR_BLUE, /* UPSTREAM */
>>> + GIT_COLOR_NORMAL, /* PLAIN */
>>> + GIT_COLOR_RED, /* REMOTE */
>>> + GIT_COLOR_NORMAL, /* LOCAL */
>>> + GIT_COLOR_GREEN, /* CURRENT */
>>> + GIT_COLOR_BLUE, /* UPSTREAM */
>>> };
>>
>>
>> What's... actually changing here? It looks like just white space? Is
>> there a strong reason for why this is changing?
>>
>> Thanks,
>> Jake
>
> None, I'm not sure how this ended up being added too.
>
> --
> Regards,
> Karthik NayakIt looks like it might just be reformatting of some spaces or stray end-spaces or something. Hard to see in an email.
Thanks, Jake