Re: Git thinks a failing command doesn't exist

From: Jeff King <peff@peff.net>
Date: Aug 11, 2010, 19:25 UTC
Message-ID: <20100811192554.GA8106@coredump.intra.peff.net>
In-Reply-To: <AANLkTin7E-v9TYd1KoD73knnSwSMy-V-pvS0TmpQd72M@mail.gmail.com>

On Wed, Aug 11, 2010 at 07:12:38PM +0000, Ævar Arnfjörð Bjarmason wrote:

Show 10 quoted lines

> Has this been noted before:
> 
>     $ git rebase --continue
>     .: 986: Can't open /home/avar/g/git/.git/rebase-merge/author-script
>     git: 'rebase' is not a git command. See 'git --help'.
>     Did you mean this?
>             rebase
> 
> Rebase failed, but the help mechanism seems to just test the exit
> code, or something similar.

Which git version and which platform? There is code in run-command to check for an exit code of 127 (which is what posix shells should produce for a missing command), and to set ENOENT in that case, which is what execv_dashed_external notices for a missing command.

So either your shell is producing that exit code for a different case, or git is broken.

-Peff