fetch output is ugly in 'next'
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | transport: pass summary_width down the callchaintransport.c | +38 | 0 replies | |
| 2/3 | fetch: pass summary_width down the callchainbuiltin/ | +21 | 0 replies | |
| 3/3 | transport: allow summary-width to be computed dynamicallybuiltin/ transport.c transport.h | +9 | 4 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] fetch output is ugly in 'next'
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(-)
Signature · 1 line
2.10.1-723-g2384e83bc3