public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: Duy Nguyen <pclouds@gmail•com>, Git Mailing List <git@vger•kernel.org>
Subject: Re: [BUG] fetch output is ugly in 'next'
Date: Fri, 21 Oct 2016 15:14:08 -0700	[thread overview]
Message-ID: <xmqqa8dxbb9r.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20161021214218.u46qf3lch3wwiutp@sigill.intra.peff.net> (Jeff King's message of "Fri, 21 Oct 2016 17:42:18 -0400")

Jeff King <peff@peff•net> writes:

> The "right" fix is to queue up the list of ref updates to print, find
> the abbreviations for each, and then print them all in one shot, knowing
> ahead of time the size necessary to align them. This could also let us
> improve the name-alignment.

Heh, that was what I was starting to code while listening to
Jonathan and Stefan talk in a meeting ;-)


  reply	other threads:[~2016-10-21 22:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21  0:26 [BUG] fetch output is ugly in 'next' Jeff King
2016-10-21 12:11 ` Duy Nguyen
2016-10-21 13:07   ` Duy Nguyen
2016-10-21 16:50     ` Junio C Hamano
2016-10-21 21:42       ` Jeff King
2016-10-21 22:14         ` Junio C Hamano [this message]
2016-10-21 22:39           ` [PATCH 0/3] " Junio C Hamano
2016-10-21 22:39             ` [PATCH 1/3] transport: pass summary_width down the callchain Junio C Hamano
2016-10-21 22:39             ` [PATCH 2/3] fetch: " Junio C Hamano
2016-10-21 22:39             ` [PATCH 3/3] transport: allow summary-width to be computed dynamically Junio C Hamano
2016-10-22  4:10               ` Jeff King
2016-10-22  4:39               ` Junio C Hamano
2016-10-22  5:04                 ` Jeff King
2016-10-22 16:25                   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqa8dxbb9r.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=pclouds@gmail$(echo .)com \
    --cc=peff@peff$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox