From: Christian Couder <christian.couder@gmail.com>
To: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Cc: Miriam Rubio <mirucam@gmail.com>, git <git@vger.kernel.org>,
Pranit Bauva <pranit.bauva@gmail.com>,
Lars Schneider <larsxschneider@gmail.com>,
Christian Couder <chriscool@tuxfamily.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Tanushree Tumane <tanushreetumane@gmail.com>,
Rafael Silva <rafaeloliveira.cs@gmail.com>
Subject: Re: [PATCH v4 1/7] bisect--helper: reimplement `bisect_log` shell function in C
Date: Sat, 30 Jan 2021 10:49:14 +0100 [thread overview]
Message-ID: <CAP8UFD0iZ5WMMV8FZgNx9jFV9W4qMMPXMEN-ExG8jOkw9LLH6g@mail.gmail.com> (raw)
In-Reply-To: <YBS6YJq0W3VsGf6P@danh.dev>
On Sat, Jan 30, 2021 at 2:46 AM Đoàn Trần Công Danh
<congdanhqx@gmail.com> wrote:
> > @@ -210,7 +205,7 @@ case "$#" in
> > replay)
> > bisect_replay "$@" ;;
> > log)
> > - bisect_log ;;
> > + git bisect--helper --bisect-log || exit ;;
>
> The original code was "die" when no bisect_log available.
>
> I think we need to "exit 1" here to indicate a failure, i.e.
>
> git bisect--helper --bisect-log || exit 1 ;;
Actually:
git bisect--helper --bisect-log || exit ;;
will indicate failure. See:
$ ( false || exit )
$ echo $?
1
The difference with what you suggest is that the exit code will be the
same instead of always 1:
$ ( ( exit 4 ) || exit )
echo $?
4
which is a good thing, as die() exits with code 128, so if `git
bisect--helper --bisect-log` die()s then we will get a 128 exit code
with `|| exit` instead of 1 with `|| exit 1`.
Thanks for your review,
Christian.
next prev parent reply other threads:[~2021-01-30 9:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 19:17 [PATCH v4 0/7] Finish converting git bisect to C part 3 Miriam Rubio
2021-01-25 19:17 ` [PATCH v4 1/7] bisect--helper: reimplement `bisect_log` shell function in C Miriam Rubio
2021-01-30 1:46 ` Đoàn Trần Công Danh
2021-01-30 9:49 ` Christian Couder [this message]
2021-01-25 19:17 ` [PATCH v4 2/7] bisect--helper: reimplement `bisect_replay` " Miriam Rubio
2021-01-29 7:51 ` Christian Couder
2021-01-25 19:17 ` [PATCH v4 3/7] bisect--helper: retire `--bisect-write` subcommand Miriam Rubio
2021-01-29 7:54 ` Christian Couder
2021-01-25 19:17 ` [PATCH v4 4/7] bisect--helper: use `res` instead of return in BISECT_RESET case option Miriam Rubio
2021-01-29 7:57 ` Christian Couder
2021-01-25 19:17 ` [PATCH v4 5/7] bisect--helper: retire `--bisect-auto-next` subcommand Miriam Rubio
2021-01-25 19:17 ` [PATCH v4 6/7] bisect--helper: reimplement `bisect_skip` shell function in C Miriam Rubio
2021-01-25 19:17 ` [PATCH v4 7/7] bisect--helper: retire `--check-and-set-terms` subcommand Miriam Rubio
2021-01-29 0:49 ` Junio C Hamano
2021-01-26 17:55 ` [PATCH v4 0/7] Finish converting git bisect to C part 3 Junio C Hamano
2021-01-26 18:27 ` Miriam R.
2021-01-26 20:05 ` Junio C Hamano
2021-01-26 22:32 ` Junio C Hamano
2021-01-27 14:12 ` Miriam R.
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=CAP8UFD0iZ5WMMV8FZgNx9jFV9W4qMMPXMEN-ExG8jOkw9LLH6g@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=mirucam@gmail.com \
--cc=pranit.bauva@gmail.com \
--cc=rafaeloliveira.cs@gmail.com \
--cc=tanushreetumane@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).