Re: [PATCH v5 0/5] Better ref summary alignment in "git fetch"

From: Duy Nguyen <pclouds@gmail.com>
Date: Jul 2, 2016, 04:39 UTC
Message-ID: <CACsJy8CLJ9aSwA_iABdDVrGULyXSgGO1A_Dy=+aOhAn1m26yDQ@mail.gmail.com>
In-Reply-To: <xmqqvb0puepd.fsf@gitster.mtv.corp.google.com>

On Sat, Jul 2, 2016 at 1:21 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 13 quoted lines

> Nguyễn Thái Ngọc Duy  <pclouds@gmail.com> writes:
>
>> I'm not sure if we should bring back "{ -> origin/}foo" format. I can
>> do it if someone still wants it.
>> ...
>> +In compact output mode, specified with configuration variable
>> +fetch.output, if either entire `<from>` or `<to>` is found in the
>> +other string, it will be substituted with `*` in the other string. For
>> +example, `master -> origin/master` becomes `master -> origin/*`.
>
> What is the desired property we would want to see in the end result
> of this series (or possible replacement of it)?  Easier to read by
> humans?  Cut-and-paste friendliness?  Alignment?

Easier to read, which is largely improved by aligning output.

Show 5 quoted lines

> I think the largest objection against "{ -> origin/}master" was that
> it wasn't cut-and-paste ready.  There might have been other attempts
> during the rerolls leading to this v5, but I have to say that what
> we ended up with, "master -> origin/*", is no more cut-and-paste
> friendly than "{ -> origin/}master".

The true cut-paste friendly is the old output, though "master -> origin/*" is a tiny bit friendlier than "{ -> origin/}master" because you can double click on master in the former to select it (origin/ requires some typing, not much with the help of tab-completion). Double clicking on "origin/}master" may or may not select master alone, depending on your terminal settings.

-- 
Duy