summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: dee48c3)
raw | patch | inline | side by side (parent: dee48c3)
author | Sergei Organov <osv@javad.com> | |
Tue, 30 Oct 2007 19:54:02 +0000 (22:54 +0300) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Tue, 30 Oct 2007 23:35:07 +0000 (16:35 -0700) |
"git-merge <msg> HEAD <other branches>" is still supported but
we shouldn't encourage its use.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
we shouldn't encourage its use.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/core-tutorial.txt | patch | blob | history |
index 6b2590d0723ad94a45c9cae174935839df3331d8..df147b5e76879851a5a95f4ddb9695786f042d56 100644 (file)
to resolve and what the merge is all about:
------------
-$ git merge "Merge work in mybranch" HEAD mybranch
+$ git merge -m "Merge work in mybranch" mybranch
------------
where the first argument is going to be used as the commit message if
------------
$ git checkout mybranch
-$ git merge "Merge upstream changes." HEAD master
+$ git merge -m "Merge upstream changes." master
------------
This outputs something like this (the actual commit object names
'commit-fix' next, like this:
------------
-$ git merge 'Merge fix in diff-fix' master diff-fix
-$ git merge 'Merge fix in commit-fix' master commit-fix
+$ git merge -m 'Merge fix in diff-fix' diff-fix
+$ git merge -m 'Merge fix in commit-fix' commit-fix
------------
Which would result in: