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

[PATCH] rebase interactive: Add hint how to continue after 'Unknown command' error

From
Steffen Prohaska <prohaska@zib.de>
Date
Jan 6, 2008, 15:46 UTC
Message-ID
<1199634385511-git-send-email-prohaska@zib.de>

rebase interactive asks the user to fix unknown commands but it did not tell how to continue.

This commits adds a hint how to continue.
Signed-off-by: Steffen Prohaska <prohaska@zib.de>
---
 git-rebase--interactive.sh |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh
index acdcc54..d4bd811 100755
--- a/git-rebase--interactive.sh
+++ b/git-rebase--interactive.sh
@@ -310,7 +310,7 @@ do_next () {
 		;;
 	*)
 		warn "Unknown command: $command $sha1 $rest"
-		die_with_patch $sha1 "Please fix this in the file $TODO."
+		die_with_patch $sha1 "Please fix this in the file $TODO. And run 'git rebase --continue'."
 		;;
 	esac
 	test -s "$TODO" && return
-- 
1.5.4.rc2.26.g1deb
Next: Wincent Colaiuta
Message 1 of 4 in “rebase interactive: Add hint how to continue after 'Unknown command' error”
  1. rebase interactive: Add hint how to continue after 'Unknown command' errorSteffen Prohaska, Jan 6, 2008
  2. Wincent ColaiutaJan 6, 2008
  3. David BrownJan 6, 2008
  4. Junio C HamanoJan 6, 2008

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.