summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: a4081ba)
raw | patch | inline | side by side (parent: a4081ba)
author | Jonathan Nieder <jrnieder@gmail.com> | |
Sat, 23 Jan 2010 09:42:46 +0000 (03:42 -0600) | ||
committer | Thomas Rast <trast@student.ethz.ch> | |
Sun, 24 Jan 2010 12:57:42 +0000 (13:57 +0100) |
The reader unfamiliar with the concepts of branching and merging
would have been completely lost. Try to help him with a diagram.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Thomas Rast <trast@student.ethz.ch>
would have been completely lost. Try to help him with a diagram.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Thomas Rast <trast@student.ethz.ch>
Documentation/git-merge.txt | patch | blob | history |
index 83bf3e783f6460ec22bd73ece1550263831883a5..e3c611dd0e5a7564c087d8d09eea8943dc509d08 100644 (file)
DESCRIPTION
-----------
-Merges the history specified by <commit> into HEAD, optionally using a
-specific merge strategy.
+Incorporates changes from the named commits (since the time their
+histories diverged from the current branch) into the current
+branch. This command is used by 'git pull' to incorporate changes
+from another repository and can be used by hand to merge changes
+from one branch into another.
+
+Assume the following history exists and the current branch is
+"`master`":
+
+------------
+ A---B---C topic
+ /
+ D---E---F---G master
+------------
+
+Then "`git merge topic`" will replay the changes made on the
+`topic` branch since it diverged from `master` (i.e., `E`) until
+its current commit (`C`) on top of `master`, and record the result
+in a new commit along with the names of the two parent commits and
+a log message from the user describing the changes.
+
+------------
+ A---B---C topic
+ / \
+ D---E---F---G---H master
+------------
The second syntax (<msg> `HEAD` <commit>...) is supported for
historical reasons. Do not use it from the command line or in