From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Matthieu Moy <Matthieu.Moy@imag.fr>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] rebase -i: fix misleading error message after 'exec no-such' instruction
Date: Tue, 18 Sep 2012 13:29:20 -0700 [thread overview]
Message-ID: <7vtxuvkrbz.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <505857CE.3050909@viscovery.net> (Johannes Sixt's message of "Tue, 18 Sep 2012 13:15:26 +0200")
Johannes Sixt <j.sixt@viscovery.net> writes:
> 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.
prev parent reply other threads:[~2012-09-18 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 11:15 [PATCH] rebase -i: fix misleading error message after 'exec no-such' instruction Johannes Sixt
2012-09-18 11:20 ` Matthieu Moy
2012-09-18 11:29 ` Johannes Sixt
2012-09-18 11:38 ` Matthieu Moy
2012-09-18 20:29 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vtxuvkrbz.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox