</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-merge</em> [-n] [--no-commit] [-s <strategy>]… <msg> <head> <remote> <remote>…</p>\r
+<div class="verseblock">\r
+<div class="content"><em>git-merge</em> [-n] [--no-commit] [--squash] [-s <strategy>]…\r
+ [--reflog-action=<action>]\r
+ -m=<msg> <remote> <remote>…</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
-<p>This is the top-level user interface to the merge machinery\r
+<p>This is the top-level interface to the merge machinery\r
which drives multiple merge strategy scripts.</p>\r
</div>\r
<h2>OPTIONS</h2>\r
</dt>\r
<dd>\r
<p>\r
- our branch head commit.\r
+ Our branch head commit. This has to be <tt>HEAD</tt>, so new\r
+ syntax does not require it\r
</p>\r
</dd>\r
<dt>\r
</dt>\r
<dd>\r
<p>\r
- other branch head merged into our branch. You need at\r
+ Other branch head merged into our branch. You need at\r
least one <remote>. Specifying more than one <remote>\r
obviously means you are trying an Octopus.\r
</p>\r
</dd>\r
+<dt>\r
+--reflog-action=<action>\r
+</dt>\r
+<dd>\r
+<p>\r
+ This is used internally when <tt>git-pull</tt> calls this command\r
+ to record that the merge was created by <tt>pull</tt> command\r
+ in the <tt>ref-log</tt> entry that results from the merge.\r
+</p>\r
+</dd>\r
</dl>\r
</div>\r
<h2>MERGE STRATEGIES</h2>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 03-Oct-2006 08:41:13 UTC\r
+Last updated 27-Nov-2006 20:03:14 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-merge' [-n] [--no-commit] [-s <strategy>]... <msg> <head> <remote> <remote>...
-
+[verse]
+'git-merge' [-n] [--no-commit] [--squash] [-s <strategy>]...
+ [--reflog-action=<action>]
+ -m=<msg> <remote> <remote>...
DESCRIPTION
-----------
-This is the top-level user interface to the merge machinery
+This is the top-level interface to the merge machinery
which drives multiple merge strategy scripts.
to give a good default for automated `git-merge` invocations.
<head>::
- our branch head commit.
+ Our branch head commit. This has to be `HEAD`, so new
+ syntax does not require it
<remote>::
- other branch head merged into our branch. You need at
+ Other branch head merged into our branch. You need at
least one <remote>. Specifying more than one <remote>
obviously means you are trying an Octopus.
+--reflog-action=<action>::
+ This is used internally when `git-pull` calls this command
+ to record that the merge was created by `pull` command
+ in the `ref-log` entry that results from the merge.
+
include::merge-strategies.txt[]
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p>git-log --pretty=short | <em>git-shortlog</em> [-h] [-n] [-s]</p>\r
+<p>git-log --pretty=short | <em>git-shortlog</em> [-h] [-n] [-s]\r
+git-shortlog [-n|--number] [-s|--summary] [<committish>…]</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 12-Oct-2006 19:10:27 UTC\r
+Last updated 27-Nov-2006 20:03:15 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
git-log --pretty=short | 'git-shortlog' [-h] [-n] [-s]
+git-shortlog [-n|--number] [-s|--summary] [<committish>...]
DESCRIPTION
-----------