From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/3] fetch output is ugly in 'next'
Date: Fri, 21 Oct 2016 15:39:24 -0700 [thread overview]
Message-ID: <20161021223927.26364-1-gitster@pobox.com> (raw)
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
next prev parent reply other threads:[~2016-10-21 22:39 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
2016-10-21 22:39 ` Junio C Hamano [this message]
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=20161021223927.26364-1-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).