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>maint
							parent
							
								
									2295e8d0c4
								
							
						
					
					
						commit
						228e2eb67e
					
				| 
						 | 
				
			
			@ -32,7 +32,7 @@ savestate() {
 | 
			
		|||
restorestate() {
 | 
			
		||||
        if test -f "$GIT_DIR/MERGE_SAVE"
 | 
			
		||||
	then
 | 
			
		||||
		git reset --hard $head
 | 
			
		||||
		git reset --hard $head >/dev/null
 | 
			
		||||
		cpio -iuv <"$GIT_DIR/MERGE_SAVE"
 | 
			
		||||
		git-update-index --refresh >/dev/null
 | 
			
		||||
	fi
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
| 
						 | 
				
			
			@ -292,6 +292,7 @@ then
 | 
			
		|||
fi
 | 
			
		||||
 | 
			
		||||
# Rewind the head to "$onto"; this saves our current head in ORIG_HEAD.
 | 
			
		||||
echo "First, rewinding head to replay your work on top of it..."
 | 
			
		||||
git-reset --hard "$onto"
 | 
			
		||||
 | 
			
		||||
# If the $onto is a proper descendant of the tip of the branch, then
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
		Reference in New Issue