From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 17 May 2017 03:41:19 GMT
Subject: Re: [PATCH v6 04/11] run-command: use the async-signal-safe execv instead of execvp
Message-ID: <xmqqr2zoxi8w.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <20170517022602.jj26pf7eypxp2fjm@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

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