From: Eric Sunshine <sunshine@sunshineco.com>
To: gitgitgadget@gmail.com
Cc: Git List <git@vger.kernel.org>,
Stefan Beller <sbeller@google.com>,
Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH v2 1/2] rebase -i: clarify what happens on a failed `exec`
Date: Wed, 10 Oct 2018 05:46:04 -0400 [thread overview]
Message-ID: <CAPig+cRMOOqGdiCqprUqiSXCa5SZDRy-kJSvdRmwY_uvynwoXQ@mail.gmail.com> (raw)
In-Reply-To: <2eefdb4874d36f14aac79b24c0f6216911f2143e.1539161632.git.gitgitgadget@gmail.com>
On Wed, Oct 10, 2018 at 4:54 AM Johannes Schindelin via GitGitGadget
<gitgitgadget@gmail.com> wrote:
> We had not documented previously what happens when an `exec` command in
> an interactive rebase fails. Now we do.
>
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> ---
> diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
> @@ -420,7 +420,8 @@ idea unless you know what you are doing (see BUGS below).
> --exec <cmd>::
> Append "exec <cmd>" after each line creating a commit in the
> final history. <cmd> will be interpreted as one or more shell
> - commands.
> + commands. Anz command that fails will interrupt the rebase,
> + withe exit code 1.
s/Anz/Any/
s/withe/with/
next prev parent reply other threads:[~2018-10-10 9:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 15:00 [PATCH 0/1] rebase -i: introduce the 'break' command Johannes Schindelin via GitGitGadget
2018-10-03 15:00 ` [PATCH 1/1] " Johannes Schindelin via GitGitGadget
2018-10-05 8:15 ` Junio C Hamano
2018-10-05 8:36 ` Jacob Keller
2018-10-05 15:36 ` Johannes Schindelin
2018-10-09 3:59 ` Junio C Hamano
2018-10-09 5:27 ` Junio C Hamano
2018-10-10 8:53 ` [PATCH v2 0/2] " Johannes Schindelin via GitGitGadget
2018-10-10 8:53 ` [PATCH v2 1/2] rebase -i: clarify what happens on a failed `exec` Johannes Schindelin via GitGitGadget
2018-10-10 9:46 ` Eric Sunshine [this message]
2018-10-11 8:15 ` Junio C Hamano
2018-10-12 8:36 ` Johannes Schindelin
2018-10-10 8:53 ` [PATCH v2 2/2] rebase -i: introduce the 'break' command Johannes Schindelin via GitGitGadget
2018-10-11 9:08 ` Phillip Wood
2018-10-12 8:35 ` Johannes Schindelin
2018-10-12 11:09 ` Phillip Wood
2018-10-12 11:24 ` Johannes Schindelin
2018-10-12 13:14 ` [PATCH v3 0/2] " Johannes Schindelin via GitGitGadget
2018-10-12 13:14 ` [PATCH v3 1/2] rebase -i: clarify what happens on a failed `exec` Johannes Schindelin via GitGitGadget
2018-10-12 13:14 ` [PATCH v3 2/2] rebase -i: introduce the 'break' command Johannes Schindelin via GitGitGadget
2018-10-12 14:09 ` Junio C Hamano
2018-10-12 15:31 ` Johannes Schindelin
2018-10-12 14:01 ` [PATCH v3 0/2] " Junio C Hamano
2018-10-12 15:32 ` Johannes Schindelin
2018-10-25 20:47 ` [PATCH 3/2] rebase -i: recognize short commands without arguments Johannes Sixt
2018-10-26 1:26 ` Junio C Hamano
2018-10-26 8:04 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cRMOOqGdiCqprUqiSXCa5SZDRy-kJSvdRmwY_uvynwoXQ@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=sbeller@google.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).