Skip to content

Commit 81646ad

Browse files
moygitster
authored andcommitted
Fix incorrect wording in git-merge.txt.
A merge is not necessarily with a remote branch, it can be with any commit. Thanks to Paolo Ciarrocchi for pointing out the problem, and to Nicolas Pitre for pointing out the fact that a merge is not necessarily with a branch head. Signed-off-by: Matthieu Moy <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent e6d1f76 commit 81646ad

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

Documentation/git-merge.txt

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,8 @@ HOW MERGE WORKS
6868
---------------
6969

7070
A merge is always between the current `HEAD` and one or more
71-
remote branch heads, and the index file must exactly match the
71+
commits (usually, branch head or tag), and the index file must
72+
exactly match the
7273
tree of `HEAD` commit (i.e. the contents of the last commit) when
7374
it happens. In other words, `git-diff --cached HEAD` must
7475
report no changes.

0 commit comments

Comments
 (0)