Thread (1 message) 1 message, 1 author, 2016-06-15

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

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:54:48

Johannes Sixt [off-list ref] writes:
From: Johannes Sixt <redacted>

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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help