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

Re: [PATCH] rebase -i: fix misleading error message after 'exec no-such' instruction

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 18, 2012, 20:29 UTC
Message-ID
<7vtxuvkrbz.fsf@alter.siamese.dyndns.org>
In-Reply-To
<505857CE.3050909@viscovery.net>
Johannes Sixt <j.sixt@viscovery.net> writes:
Show 19 quoted lines
> From: Johannes Sixt <j6t@kdbg.org>
>
> When the todo sheet of interactive rebase instructs to run a non-existing
> command, the operation stops with the following error:
>
>   Execution failed: no-such
>   You can fix the problem, and then run
>
>           git rebase --continue
>
>   fatal: 'rebase' appears to be a git command, but we were not
>   able to execute it. Maybe git-rebase is broken?
>
> The reason is that the shell that attempted to run the command exits with
> code 127. rebase--interactive just forwards this code to the caller (the
> git wrapper). But our smart run-command infrastructure detects this
> special exit code and turns it into ENOENT, which in turn is interpreted
> by the git wrapper as if the external command that it just executed did
> not exist.

That's a funny one ;-) Will queue. Thanks.

Previous: Matthieu Moy
Message 5 of 5 in “rebase -i: fix misleading error message after 'exec no-such' instruction”
  1. rebase -i: fix misleading error message after 'exec no-such' instructionJohannes Sixt, Sep 18, 2012
  2. Matthieu MoySep 18, 2012
  3. Johannes SixtSep 18, 2012
  4. Matthieu MoySep 18, 2012
  5. Junio C HamanoSep 18, 2012

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.