Duy Nguyen <pclo...@gmail.com> writes:
> On Mon, May 23, 2016 at 7:58 AM, Junio C Hamano <gits...@pobox.com> wrote:
>> That is, I wonder if the above can become something like:
>>
>>> From github.com:pclouds/git
>>> * [new branch] { -> pclouds/}2nd-index
>>> * [new branch] { -> pclouds/}3nd-index
>>> * [new branch] { -> pclouds/}file-watcher
>>> ...
>
> for context of the following quote...
>
> On Thu, May 26, 2016 at 12:18 PM, Jeff King <p...@peff.net> wrote:
>> I do agree with Junio that we could probably improve the output quite a
>> bit by not showing each refname twice in the common case. I don't quite
>> find the "{ -> origin/}whatever" particularly pretty, but something like
>> that which keeps the variable bits at the end would make this problem
>> just go away.
>
> I tried it out. It's a bit hard to read at the "/}" boundary. Color
> highlight might help. But it occurs to me, could we extend refspec a
> bit to allow "foo/bar:base/..." be be equivalent of
> "foo/bar:base/foo/bar". Then fetch output could become
>
>>> * [new branch] 2nd-index:pclouds/...
>>> * [new branch] 3nd-index:pclouds/...
>>> * [new branch] file-watcher:pclouds/...
>
> It might be a tiny bit better, and a forced update could be displayed
> with a prefix '+'. Hmm?
I do not find that "..." particularly more readable, but that
probably is very subjective. It is much less copy&pastable, when
compared to pasting "pclouds/}2nd-index" and then removing "}".
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
