Re: [PATCH 00/18] Add `branch-diff`, a `tbdiff` lookalike
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- May 4, 2018, 07:24 UTC
- Message-ID
- <nycvar.QRO.7.76.6.1805040923570.77@tvgsbejvaqbjf.bet>
- In-Reply-To
- <xmqq1sest2m1.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Fri, 4 May 2018, Junio C Hamano wrote:
Show 33 quoted lines
> Johannes Schindelin <johannes.schindelin@gmx.de> writes: > > > Johannes Schindelin (17): > > Add a function to solve least-cost assignment problems > > Add a new builtin: branch-diff > > branch-diff: first rudimentary implementation > > branch-diff: improve the order of the shown commits > > branch-diff: also show the diff between patches > > branch-diff: right-trim commit messages > > branch-diff: indent the diffs just like tbdiff > > branch-diff: suppress the diff headers > > branch-diff: adjust the output of the commit pairs > > branch-diff: do not show "function names" in hunk headers > > branch-diff: use color for the commit pairs > > color: provide inverted colors, too > > diff: add an internal option to dual-color diffs of diffs > > branch-diff: offer to dual-color the diffs > > branch-diff --dual-color: work around bogus white-space warning > > branch-diff: add a man page > > completion: support branch-diff > > > > Thomas Rast (1): > > branch-diff: add tests > > Lovely. > > I often have to criticize a series whose later half consists of many > follow-up patches with "don't do 'oops, the previous was wrong'", > but the follow-up patches in this series are not such corrections. > The organization of the series to outline the basic and core idea > first in the minimum form and then to build on it to improve an > aspect of the command one step at a time is very helpful to guide > the readers where the author of the series wants them to go.
Thanks! *beams*
Ciao, Dscho