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

[PATCH] git-rebase documentation: explain the exit code of custom commands

From
Stefan Beller <sbeller@google.com>
Date
Dec 29, 2014, 22:30 UTC
Message-ID
<1419892207-26687-1-git-send-email-sbeller@google.com>
Signed-off-by: Stefan Beller <sbeller@google.com>
---
 Documentation/git-rebase.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
index 924827d..ffadb0b 100644
--- a/Documentation/git-rebase.txt
+++ b/Documentation/git-rebase.txt
@@ -372,7 +372,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. Rebasing will stop for manual inspection if the command
+	returns a non zero exit code.
 +
 This option can only be used with the `--interactive` option
 (see INTERACTIVE MODE below).
-- 
2.2.1.62.g3f15098
Next: Junio C Hamano
Message 1 of 5 in “git-rebase documentation: explain the exit code of custom commands”
  1. git-rebase documentation: explain the exit code of custom commandsStefan Beller, Dec 29, 2014
  2. Junio C HamanoDec 30, 2014
  3. Stefan BellerDec 30, 2014
  4. Stefan BellerDec 30, 2014
  5. Junio C HamanoDec 30, 2014

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.