summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: e6d1f76)
raw | patch | inline | side by side (parent: e6d1f76)
author | Matthieu Moy <Matthieu.Moy@imag.fr> | |
Mon, 3 Mar 2008 17:52:49 +0000 (18:52 +0100) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Mon, 3 Mar 2008 21:40:15 +0000 (13:40 -0800) |
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 <Matthieu.Moy@imag.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
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 <Matthieu.Moy@imag.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-merge.txt | patch | blob | history |
index 0c9ad7f2bbdf4872882d127804e7c474729c0818..c136b1069230af55b62ba95a1b40bdcc019b7b42 100644 (file)
---------------
A merge is always between the current `HEAD` and one or more
-remote branch heads, and the index file must exactly match the
+commits (usually, branch head or tag), and the index file must
+exactly match the
tree of `HEAD` commit (i.e. the contents of the last commit) when
it happens. In other words, `git-diff --cached HEAD` must
report no changes.