Re: [PATCH v6 04/11] run-command: use the async-signal-safe execv instead of execvp

From: Junio C Hamano <gitster@pobox.com>
Date: May 17, 2017, 03:41 UTC
Message-ID: <xmqqr2zoxi8w.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <20170517022602.jj26pf7eypxp2fjm@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 6 quoted lines

> This is about finding "/usr/bin/foo", realizing it cannot be exec'd
> because it lacks a shebang line, and then pretending that it did have
> "#!/bin/sh". IOW, maintaining compatibility with execvp().
>
> So the command itself isn't a shell command, but it may execute a shell
> script. If that makes sense.

Ah, OK.  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.