git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [BUG] fetch output is ugly in 'next'

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 21, 2016, 22:14 UTC
Message-ID
<xmqqa8dxbb9r.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20161021214218.u46qf3lch3wwiutp@sigill.intra.peff.net>
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 ;-)

Previous: Jeff KingNext: Junio C Hamano
Message 6 of 14 in “[BUG] fetch output is ugly in 'next'”
  1. Jeff KingOct 21, 2016
  2. Duy NguyenOct 21, 2016
  3. Duy NguyenOct 21, 2016
  4. Junio C HamanoOct 21, 2016
  5. Jeff KingOct 21, 2016
  6. Junio C HamanoOct 21, 2016
  7. 0/3 fetch output is ugly in 'next'Junio C Hamano, Oct 21, 2016
  8. 2/3 fetch: pass summary_width down the callchainJunio C Hamano, Oct 21, 2016
  9. 1/3 transport: pass summary_width down the callchainJunio C Hamano, Oct 21, 2016
  10. 3/3 transport: allow summary-width to be computed dynamicallyJunio C Hamano, Oct 21, 2016
  11. Jeff KingOct 22, 2016
  12. Junio C HamanoOct 22, 2016
  13. Jeff KingOct 22, 2016
  14. Junio C HamanoOct 22, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.