summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 55e1805)
raw | patch | inline | side by side (parent: 55e1805)
author | Junio C Hamano <junkio@cox.net> | |
Fri, 28 Apr 2006 09:32:44 +0000 (02:32 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Fri, 28 Apr 2006 09:32:44 +0000 (02:32 -0700) |
After doing the hard work of hand resolving the conflicts in the
working tree, if the user forgets to run update-index to mark
the paths that have been resolved, the command gave an
unfriendly "fatal: git-write-tree: not able to write tree" error
message. Catch the situation early and give more meaningful
message and suggestion.
Noticed and suggested by Len Brown.
Signed-off-by: Junio C Hamano <junkio@cox.net>
working tree, if the user forgets to run update-index to mark
the paths that have been resolved, the command gave an
unfriendly "fatal: git-write-tree: not able to write tree" error
message. Catch the situation early and give more meaningful
message and suggestion.
Noticed and suggested by Len Brown.
Signed-off-by: Junio C Hamano <junkio@cox.net>
git-am.sh | patch | blob | history |
diff --git a/git-am.sh b/git-am.sh
index eab4aa891e522539bb145c9702200d3a788e650c..872145b92dc7000eb1c87d548a46fa0d9522870d 100755 (executable)
--- a/git-am.sh
+++ b/git-am.sh
echo "No changes - did you forget update-index?"
stop_here $this
fi
+ unmerged=$(git-ls-files -u)
+ if test -n "$unmerged"
+ then
+ echo "You still have unmerged paths in your index"
+ echo "did you forget update-index?"
+ stop_here $this
+ fi
apply_status=0
;;
esac