diff --git a/git-applypatch.sh b/git-applypatch.sh
index e8ba34a0ad4a466083c8462cc038de9d8ad6a4ab..8df2aee4c2d031ac10c66af0a079bd022c281c0d 100755 (executable)
--- a/git-applypatch.sh
+++ b/git-applypatch.sh
USAGE='<msg> <patch> <info> [<signoff>]'
. git-sh-setup
-case "$#" in 3|4) usage ;; esac
+case "$#" in 3|4) ;; *) usage ;; esac
final=.dotest/final-commit
##
# This is not so wrong. Depending on which base we picked,
# orig_tree may be wildly different from ours, but his_tree
# has the same set of wildly different changes in parts the
- # patch did not touch, so resolve ends up cancelling them,
+ # patch did not touch, so resolve ends up canceling them,
# saying that we reverted all those changes.
if git-merge-resolve $orig_tree -- HEAD $his_tree
parent=$(git-rev-parse --verify HEAD) &&
commit=$(git-commit-tree $tree -p $parent <"$final") || exit 1
echo Committed: $commit
-git-update-ref HEAD $commit $parent || exit
+git-update-ref -m "applypatch: $SUBJECT" HEAD $commit $parent || exit
if test -x "$GIT_DIR"/hooks/post-applypatch
then