Skip to content

Commit

Permalink
core-tutorial: Use new syntax for git-merge.
Browse files Browse the repository at this point in the history
"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>
  • Loading branch information
Sergei Organov authored and Junio C Hamano committed Oct 30, 2007
1 parent dee48c3 commit ba17892
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions Documentation/core-tutorial.txt
Original file line number Diff line number Diff line change
Expand Up @@ -883,7 +883,7 @@ script called `git merge`, which wants to know which branches you want
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
Expand Down Expand Up @@ -970,7 +970,7 @@ to the `master` branch. Let's go back to `mybranch`, and run

------------
$ 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
Expand Down Expand Up @@ -1613,8 +1613,8 @@ in both of them. You could merge in 'diff-fix' first and then
'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:
Expand Down

0 comments on commit ba17892

Please sign in to comment.