Re: [PATCH 1/2] fetch: better alignment in ref summary

From: Jeff King <peff@peff.net>
Date: May 26, 2016, 16:29 UTC
Message-ID: <20160526162940.GB18210@sigill.intra.peff.net>
In-Reply-To: <574706A1.8040606@xiplink.com>

On Thu, May 26, 2016 at 10:22:25AM -0400, Marc Branchaud wrote:

Show 8 quoted lines

> 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-watcher

That covers the common case of:

  refs/heads/*:refs/remotes/pclouds/*

but sometimes the remote and local names are not the same, and the mapping is interesting. Like:

  $ git fetch origin refs/pull/*/head:refs/remotes/pr/*
  ...
   * [new ref]         refs/pull/77/head -> pr/77

Or even:

  $ git fetch origin refs/pull/77/head refs/pull/78/head
  From ...
   * branch            refs/pull/77/head -> FETCH_HEAD
   * branch            refs/pull/78/head -> FETCH_HEAD

So I think we need a scheme that can show the interesting mappings, but collapses to something simple for the common case.

-Peff