summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: ed4a6ba)
raw | patch | inline | side by side (parent: ed4a6ba)
author | Jonathan Nieder <jrnieder@gmail.com> | |
Sat, 23 Jan 2010 09:33:37 +0000 (03:33 -0600) | ||
committer | Thomas Rast <trast@student.ethz.ch> | |
Sun, 24 Jan 2010 12:57:42 +0000 (13:57 +0100) |
So the section layout changes as follows:
NAME
SYNOPSIS
DESCRIPTION
OPTIONS
-MERGE STRATEGIES
HOW MERGE WORKS
HOW CONFLICTS ARE PRESENTED
HOW TO RESOLVE CONFLICTS
EXAMPLES
+MERGE STRATEGIES
CONFIGURATION
SEE ALSO
AUTHOR
DOCUMENTATION
GIT
NOTES
The first-time user will care more about conflicts than about
strategies other than 'recursive'.
One of the examples uses -s ours, but I do not think this hinders
readability.
Suggested-by: Thomas Rast <trast@student.ethz.ch>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Thomas Rast <trast@student.ethz.ch>
NAME
SYNOPSIS
DESCRIPTION
OPTIONS
-MERGE STRATEGIES
HOW MERGE WORKS
HOW CONFLICTS ARE PRESENTED
HOW TO RESOLVE CONFLICTS
EXAMPLES
+MERGE STRATEGIES
CONFIGURATION
SEE ALSO
AUTHOR
DOCUMENTATION
GIT
NOTES
The first-time user will care more about conflicts than about
strategies other than 'recursive'.
One of the examples uses -s ours, but I do not think this hinders
readability.
Suggested-by: Thomas Rast <trast@student.ethz.ch>
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 1fecedbbcf01bfcf5b80176b9406203ac9089d87..83bf3e783f6460ec22bd73ece1550263831883a5 100644 (file)
You need at least one <commit>. Specifying more than one
<commit> obviously means you are trying an Octopus.
-include::merge-strategies.txt[]
-
HOW MERGE WORKS
---------------
release/version name would be acceptable.
+include::merge-strategies.txt[]
+
CONFIGURATION
-------------
include::merge-config.txt[]