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

[PATCH] A more sensible error message why 'git rebase --continue' failed

From
EPEvan Phoenix <evan@fallingsnow.net>
Date
Aug 20, 2007, 01:13 UTC
Message-ID
<11875724181583-git-send-email-evan@fallingsnow.net>

The current message is a bit cryptic, indicating that only changes which contained merge conflicts should be added to the index, but in fact, all outstanding changes must be.

The change could also incorporate a -i that prompts the user and performs 'git add -u' if they wish, allowing the rebase to properly continue.

Signed-off-by: Evan Phoenix <evan@fallingsnow.net>
diff --git a/git-rebase.sh b/git-rebase.sh
index cbafa14..c67f29a 100755
--- a/git-rebase.sh
+++ b/git-rebase.sh
@@ -135,8 +135,12 @@ do
 	case "$1" in
 	--continue)
 		git diff-files --quiet || {
-			echo "You must edit all merge conflicts and then"
-			echo "mark them as resolved using git add"
+                        echo "Unable to continue rebase:"
+                        echo "  All modified files must be added to index first."
+                        echo "  Use 'git add' to resolve them and add them to the index."
+                        echo
+                        echo "Outstanding files:"
+                        git diff-files --name-status
 			exit 1
 		}
 		if test -d "$dotest"
-- 
1.5.3.rc5.41.gc1c22
Next: Junio C Hamano
Message 1 of 5 in “A more sensible error message why 'git rebase --continue' failed”
  1. A more sensible error message why 'git rebase --continue' failedEvan Phoenix, Aug 20, 2007
  2. Junio C HamanoAug 20, 2007
  3. Evan PhoenixAug 20, 2007
  4. Steven GrimmAug 20, 2007
  5. Johannes SixtAug 20, 2007

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.