Re: [PATCH v4 00/21] Add `range-diff`, a `tbdiff` lookalike

Johannes Schindelin [off-list ref] writes:

I'll just try to get that option parsing change in that Eric suggested,
force-push, then wait for macOS and Linux builds to pass (trusting that
Windows will follow suite) and hit /submit.

OK.  Obviously receiving, applying and inspecting that result will
not be done in time for today's integration cycle, but having a
version that limits its cope and is suitable for 'next' is a good
thing to have at this point during the cycle.  Correct whitespace
error colouring, etc., can be done on top after the basics settle,
and the basics were good in a few versions ago already IIRC.

Hi Junio,

On Fri, 10 Aug 2018, Junio C Hamano wrote:

Johannes Schindelin [off-list ref] writes:

quoted

I'll just try to get that option parsing change in that Eric suggested,
force-push, then wait for macOS and Linux builds to pass (trusting that
Windows will follow suite) and hit /submit.

OK.  Obviously receiving, applying and inspecting that result will
not be done in time for today's integration cycle, but having a
version that limits its cope and is suitable for 'next' is a good
thing to have at this point during the cycle.  Correct whitespace
error colouring, etc., can be done on top after the basics settle,
and the basics were good in a few versions ago already IIRC.

No, a couple of issues were identified, still, that merited several dozen
rebases on my side.

Ciao,
Dscho