Re: [PATCH 00/11] Finish converting git bisect into a built-in

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jan 28, 2022, 12:42 UTC
Message-ID: <nycvar.QRO.7.76.6.2201281336410.347@tvgsbejvaqbjf.bet>
In-Reply-To: <CAN7CjDC+O883DB1iaJAXF5ZCis7FP2Z9z0y2qS2-JVAKfQA8aA@mail.gmail.com>

Hi Miriam,

On Fri, 28 Jan 2022, Miriam R. wrote:

> I had done the last commits to finish the porting of git bisect command
> since my Outreachy internship two years ago (
> https://gitlab.com/mirucam/git/-/commits/git-bisect-work-part5-v1), and I
> was planning to send them in the last patch series during this February.

Oh sorry! I specifically went to look at your fork before starting to work on the patch series, but had not seen that branch. Now I updated my remote-tracking branches and see it as a new branch, so I am not sure whether I missed it or whether it simply wasn't there.

All in all, we did very similar things. I have a slight preference for the more concise version that does not use any command modes (and therefore also does not duplicate the commands in the output of `git bisect -h`).

Maybe you could find time in February to review my patch series? Not a big deal if you're too busy.

Ciao, Dscho