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

[PATCH 0/3] fetch output is ugly in 'next'

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 21, 2016, 22:39 UTC
Message-ID
<20161021223927.26364-1-gitster@pobox.com>
In-Reply-To
<xmqqa8dxbb9r.fsf@gitster.mtv.corp.google.com>

It turns out that there are three codepaths, all of which have a set of refs that they want to show them using TRANSPORT_SUMMARY_WIDTH constant. The two preparatory steps turn the constant used at the leaf level into a parameter that is passed down through these callchains, and the last step introduces a helper function that can be used to compute the appropriate width to be fed to these callchains.

Junio C Hamano (3):
  transport: pass summary_width down the callchain
  fetch: pass summary_width down the callchain
  transport: allow summary-width to be computed dynamically
 builtin/fetch.c | 37 +++++++++++++++++--------------
 transport.c     | 68 ++++++++++++++++++++++++++++++++++++---------------------
 transport.h     |  2 +-
 3 files changed, 65 insertions(+), 42 deletions(-)
-- 
2.10.1-723-g2384e83bc3
Previous: Junio C HamanoNext: Junio C Hamano
Message 7 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.