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

From: Miriam R. <mirucam@gmail.com>
Date: Jan 28, 2022, 15:11 UTC
Message-ID: <CAN7CjDC+A08tq-6bfxMUH_VcEZHVOr=BpWEiuuinBj7ufnch3g@mail.gmail.com>
In-Reply-To: <nycvar.QRO.7.76.6.2201281336410.347@tvgsbejvaqbjf.bet>

El vie, 28 ene 2022 a las 13:42, Johannes Schindelin (<Johannes.Schindelin@gmx.de>) escribió:

Show 14 quoted lines

>
> 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.

Hi Johannes,

the branch ..part5-v1, I think it is from the last month, but the commits were done like two years ago during my internship and they were also in this branch (https://gitlab.com/mirucam/git/-/commits/git-bisect-work4.7). But don’t worry. Of course your patch series will be way better.

Show 8 quoted lines

>
> 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.
>

Haha, I could review it, but I am sure they will be perfect. Ciao, Miriam.

> Ciao,
> Dscho