Re: git bisect bad @

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 13, 2022, 18:40 UTC
Message-ID: <xmqqr19biinm.fsf@gitster.g>
In-Reply-To: <8bc73981-589e-20e5-247b-2f74e166ae1a@web.de>

René Scharfe <l.s.r@web.de> writes:

> The implementation language of git bisect is not immediately relevant
> here, but that the shell is used to call the user-supplied bisect run
> script is.  If we'd run it directly (without RUN_USING_SHELL) we could
> distinguish error code 126/127 from execution errors.

Yes, but it means that we'd need to reimplement command line splitting, environment and variable substitutions, etc. in a way that people expect from executing their run "script" with a shell.

I'd rather not to see us go there.

Thanks.

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