From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Miriam Rubio <mirucam@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v8 0/6] Finish converting git bisect to C part 2 subset 1
Date: Wed, 23 Sep 2020 16:46:49 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2009231645380.5061@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20200923072740.20772-1-mirucam@gmail.com>
Hi Miriam,
On Wed, 23 Sep 2020, Miriam Rubio wrote:
> General changes
> ---------------
>
> * Rebased on 385c171a01, (Fifteenth batch, 2020-09-18) to update command
> help messages.
>
>
> Specific changes
> ----------------
>
>
> [4/6] bisect--helper: reimplement `bisect_autostart` shell function in C
>
> * Amend commit message.
> * Change to `return -1` when we cannot autostart.
> * Add `|| exit` to bisect-autostart call in shell script.
I think the `bisect_next` function needs the same treatment. Other than
that, this iteration is ready to go from my side.
Thank you,
Dscho
next prev parent reply other threads:[~2020-09-23 18:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 7:27 [PATCH v8 0/6] Finish converting git bisect to C part 2 subset 1 Miriam Rubio
2020-09-23 7:27 ` [PATCH v8 1/6] bisect--helper: BUG() in cmd_*() on invalid subcommand Miriam Rubio
2020-09-23 7:27 ` [PATCH v8 2/6] bisect--helper: use '-res' in 'cmd_bisect__helper' return Miriam Rubio
2020-09-23 7:27 ` [PATCH v8 3/6] bisect--helper: introduce new `write_in_file()` function Miriam Rubio
2020-09-23 7:27 ` [PATCH v8 4/6] bisect--helper: reimplement `bisect_autostart` shell function in C Miriam Rubio
2020-09-23 14:41 ` Johannes Schindelin
2020-09-23 7:27 ` [PATCH v8 5/6] bisect: call 'clear_commit_marks_all()' in 'bisect_next_all()' Miriam Rubio
2020-09-23 7:27 ` [PATCH v8 6/6] bisect--helper: reimplement `bisect_next` and `bisect_auto_next` shell functions in C Miriam Rubio
2020-09-23 14:46 ` Johannes Schindelin [this message]
2020-09-23 16:14 ` [PATCH v8 0/6] Finish converting git bisect to C part 2 subset 1 Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.2009231645380.5061@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mirucam@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).