Re: [PATCH 1/2] fetch: better alignment in ref summary
- From
Marc Branchaud <marcnarc@xiplink.com>
- Date
- May 26, 2016, 14:22 UTC
- Message-ID
- <574706A1.8040606@xiplink.com>
- In-Reply-To
- <CACsJy8BS2n8T1smxEJMPNiXBvMYHWnQ9BQGk_OKqJd1GFcuk7w@mail.gmail.com>
On 2016-05-22 09:59 PM, Duy Nguyen wrote:
Show 20 quoted lines
> On Mon, May 23, 2016 at 7:58 AM, Junio C Hamano <gitster@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
>>> ...
>>
>> The above example borrows the idea used in diffstat label for
>> renaming patch and I think you can design a better notataion, but a
>> big point is that you can shorten the whole thing by not repeating
>> the common part twice. The arrow aligns merely as a side effect of
>> the shortening, taking advantage of the fact that most people fetch
>> with "$their_prefix/*:$our_prefix/*" renaming refspec.
>
> I did think of that. My only concern is, with the new output I can't
> simply copy the ref name (e.g. pclouds/2nd-index) and use it to, say,
> examine with git-log. But I'm more of a "tab tab tab" person than
> "copy and paste", so I don't know how often people need to do that.Why do we need any kind of "->" at all? How about simply (with an update to "old-branch" for comparison to probably-more-common output):
From github.com:pclouds/git
cafed0c..badfeed pclouds/old-branch
* [new branch] pclouds/2nd-index
* [new branch] pclouds/3nd-index
* [new branch] pclouds/file-watcherM.