git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v4 1/7] bisect--helper: reimplement `bisect_log` shell function in C

From
Đoàn Trần Công Danh <congdanhqx@gmail.com>
Date
Jan 30, 2021, 01:46 UTC
Message-ID
<YBS6YJq0W3VsGf6P@danh.dev>
In-Reply-To
<20210125191710.45161-2-mirucam@gmail.com>
Show 10 quoted lines
> +static enum bisect_error bisect_log(void)
> +{
> +	int fd, status;
> +	fd = open(git_path_bisect_log(), O_RDONLY);
> +	if (fd < 0)
> +		return BISECT_FAILED;
> +
> +	status = copy_fd(fd, STDOUT_FILENO);
> +	close(fd);
> +	return status ? BISECT_FAILED : BISECT_OK;
The old code will write "We are not bisection." to stderr when, well,
we're not bisecting. This message suggested an alternative
 https://lore.kernel.org/git/gohp6kv9bml9qc.fsf@gmail.com
Show 58 quoted lines
> +}
> +
>  int cmd_bisect__helper(int argc, const char **argv, const char *prefix)
>  {
>  	enum {
> @@ -916,7 +928,8 @@ int cmd_bisect__helper(int argc, const char **argv, const char *prefix)
>  		BISECT_AUTOSTART,
>  		BISECT_NEXT,
>  		BISECT_AUTO_NEXT,
> -		BISECT_STATE
> +		BISECT_STATE,
> +		BISECT_LOG
>  	} cmdmode = 0;
>  	int res = 0, nolog = 0;
>  	struct option options[] = {
> @@ -938,6 +951,8 @@ int cmd_bisect__helper(int argc, const char **argv, const char *prefix)
>  			 N_("verify the next bisection state then checkout the next bisection commit"), BISECT_AUTO_NEXT),
>  		OPT_CMDMODE(0, "bisect-state", &cmdmode,
>  			 N_("mark the state of ref (or refs)"), BISECT_STATE),
> +		OPT_CMDMODE(0, "bisect-log", &cmdmode,
> +			 N_("list the bisection steps so far"), BISECT_LOG),
>  		OPT_BOOL(0, "no-log", &nolog,
>  			 N_("no log for BISECT_WRITE")),
>  		OPT_END()
> @@ -1000,6 +1015,11 @@ int cmd_bisect__helper(int argc, const char **argv, const char *prefix)
>  		get_terms(&terms);
>  		res = bisect_state(&terms, argv, argc);
>  		break;
> +	case BISECT_LOG:
> +		if (argc)
> +			return error(_("--bisect-log requires 0 arguments"));
> +		res = bisect_log();
> +		break;
>  	default:
>  		BUG("unknown subcommand %d", cmdmode);
>  	}
> diff --git a/git-bisect.sh b/git-bisect.sh
> index 1f3f6e9fc5..05863cc142 100755
> --- a/git-bisect.sh
> +++ b/git-bisect.sh
> @@ -169,11 +169,6 @@ exit code \$res from '\$command' is < 0 or >= 128" >&2
>  	done
>  }
>  
> -bisect_log () {
> -	test -s "$GIT_DIR/BISECT_LOG" || die "$(gettext "We are not bisecting.")"
> -	cat "$GIT_DIR/BISECT_LOG"
> -}
> -
>  get_terms () {
>  	if test -s "$GIT_DIR/BISECT_TERMS"
>  	then
> @@ -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 ;;
Show 6 quoted lines
>  	run)
>  		bisect_run "$@" ;;
>  	terms)
> -- 
> 2.29.2
> 
-- 
Danh
Previous: Miriam RubioNext: Christian Couder
Message 3 of 19 in “Finish converting git bisect to C part 3”
  1. 0/7 Finish converting git bisect to C part 3Miriam Rubio, Jan 25, 2021
  2. 1/7 bisect--helper: reimplement `bisect_log` shell function in CMiriam Rubio, Jan 25, 2021
  3. Đoàn Trần Công DanhJan 30, 2021
  4. Christian CouderJan 30, 2021
  5. 7/7 bisect--helper: retire `--check-and-set-terms` subcommandMiriam Rubio, Jan 25, 2021
  6. Junio C HamanoJan 29, 2021
  7. 4/7 bisect--helper: use `res` instead of return in BISECT_RESET case optionMiriam Rubio, Jan 25, 2021
  8. Christian CouderJan 29, 2021
  9. 6/7 bisect--helper: reimplement `bisect_skip` shell function in CMiriam Rubio, Jan 25, 2021
  10. 5/7 bisect--helper: retire `--bisect-auto-next` subcommandMiriam Rubio, Jan 25, 2021
  11. 3/7 bisect--helper: retire `--bisect-write` subcommandMiriam Rubio, Jan 25, 2021
  12. Christian CouderJan 29, 2021
  13. 2/7 bisect--helper: reimplement `bisect_replay` shell function in CMiriam Rubio, Jan 25, 2021
  14. Christian CouderJan 29, 2021
  15. Junio C HamanoJan 26, 2021
  16. Miriam R.Jan 26, 2021
  17. Junio C HamanoJan 26, 2021
  18. Junio C HamanoJan 26, 2021
  19. Miriam R.Jan 27, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.