author | Junio C Hamano <junkio@cox.net> | |
Fri, 22 Dec 2006 23:21:55 +0000 (15:21 -0800) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Fri, 22 Dec 2006 23:21:55 +0000 (15:21 -0800) | ||
commit | 228e2eb67e9f15983519f472cc1566a3dd857f9c | |
tree | 2ba0c8bf7369621e825bf1e9f486e64abf52ff61 | tree | snapshot |
parent | 2295e8d0c4cec41fbe257ddb957516a7c1a139df | commit | diff |
merge and reset: adjust for "reset --hard" messages
An earlier commit made "reset --hard" chattier but leaking its
message from "git rebase" (which calls it when first rewinding
the current branch to prepare replaying our own changes) without
explanation was confusing, so add an extra message to mention
it. Inside restorestate in merge (which is rarely exercised
codepath, where more than one strategies are attempted),
resetting to the original state uses "reset --hard" -- this can
be squelched entirely.
Signed-off-by: Junio C Hamano <junkio@cox.net>
An earlier commit made "reset --hard" chattier but leaking its
message from "git rebase" (which calls it when first rewinding
the current branch to prepare replaying our own changes) without
explanation was confusing, so add an extra message to mention
it. Inside restorestate in merge (which is rarely exercised
codepath, where more than one strategies are attempted),
resetting to the original state uses "reset --hard" -- this can
be squelched entirely.
Signed-off-by: Junio C Hamano <junkio@cox.net>
git-merge.sh | diff | blob | history | |
git-rebase.sh | diff | blob | history |