<div class="content"><em>git-show-branch</em> [--all] [--remotes] [--topo-order] [--current]\r
[--more=<n> | --list | --independent | --merge-base]\r
[--no-name | --sha1-name] [--topics] [<rev> | <glob>]…\r
-<em>git-show-branch</em> (-g|--reflog)[=<n>[,<base>]] [--list] <ref></div></div>\r
+<em>git-show-branch</em> (-g|--reflog)[=<n>[,<base>]] [--list] [<ref>]</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
</p>\r
</dd>\r
<dt>\r
---reflog[=<n>[,<base>]] <ref>\r
+--reflog[=<n>[,<base>]] [<ref>]\r
</dt>\r
<dd>\r
<p>\r
Shows <n> most recent ref-log entries for the given\r
ref. If <base> is given, <n> entries going back from\r
that entry. <base> can be specified as count or date.\r
- <tt>-g</tt> can be used as a short-hand for this option.\r
+ <tt>-g</tt> can be used as a short-hand for this option. When\r
+ no explicit <ref> parameter is given, it defaults to the\r
+ current branch (or <tt>HEAD</tt> if it is detached).\r
</p>\r
</dd>\r
</dl>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 25-Jan-2007 02:23:49 UTC\r
+Last updated 05-Feb-2007 07:21:36 UTC\r
</div>\r
</div>\r
</body>\r
'git-show-branch' [--all] [--remotes] [--topo-order] [--current]
[--more=<n> | --list | --independent | --merge-base]
[--no-name | --sha1-name] [--topics] [<rev> | <glob>]...
-'git-show-branch' (-g|--reflog)[=<n>[,<base>]] [--list] <ref>
+'git-show-branch' (-g|--reflog)[=<n>[,<base>]] [--list] [<ref>]
DESCRIPTION
-----------
will show the revisions given by "git rev-list {caret}master
topic1 topic2"
---reflog[=<n>[,<base>]] <ref>::
+--reflog[=<n>[,<base>]] [<ref>]::
Shows <n> most recent ref-log entries for the given
ref. If <base> is given, <n> entries going back from
that entry. <base> can be specified as count or date.
- `-g` can be used as a short-hand for this option.
+ `-g` can be used as a short-hand for this option. When
+ no explicit <ref> parameter is given, it defaults to the
+ current branch (or `HEAD` if it is detached).
Note that --more, --list, --independent and --merge-base options
are mutually exclusive.
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
-<p><em>git-symbolic-ref</em> [-q] <name> [<ref>]</p>\r
+<p><em>git-symbolic-ref</em> [-q] [-m <reason>] <name> [<ref>]</p>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
non-zero status silently.\r
</p>\r
</dd>\r
+<dt>\r
+-m\r
+</dt>\r
+<dd>\r
+<p>\r
+ Update the reflog for <name> with <reason>. This is valid only\r
+ when creating or updating a symbolic ref.\r
+</p>\r
+</dd>\r
</dl>\r
</div>\r
<h2>NOTES</h2>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 19-Jan-2007 00:37:35 UTC\r
+Last updated 05-Feb-2007 07:21:36 UTC\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
-'git-symbolic-ref' [-q] <name> [<ref>]
+'git-symbolic-ref' [-q] [-m <reason>] <name> [<ref>]
DESCRIPTION
-----------
symbolic ref but a detached HEAD; instead exit with
non-zero status silently.
+-m::
+ Update the reflog for <name> with <reason>. This is valid only
+ when creating or updating a symbolic ref.
+
NOTES
-----
In the past, `.git/HEAD` was a symbolic link pointing at
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 04-Feb-2007 08:31:47 UTC\r
+Last updated 05-Feb-2007 07:21:37 UTC\r
</div>\r
</div>\r
</body>\r
this branch. If this branch is the only branch containing those\r
commits, they will be lost. Also, don't use "git reset" on a\r
publicly-visible branch that other developers pull from, as it will\r
-force needless merges on other developers to clean up the history.</p>\r
+force needless merges on other developers to clean up the history.\r
+If you need to undo changes that you have pushed, use <a href="git-revert.html">git-revert(1)</a>\r
+instead.</p>\r
<p>The git grep command can search for strings in any version of your\r
project, so</p>\r
<div class="listingblock">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 04-Feb-2007 08:31:49 UTC\r
+Last updated 05-Feb-2007 07:21:39 UTC\r
</div>\r
</div>\r
</body>\r
commits, they will be lost. Also, don't use "git reset" on a
publicly-visible branch that other developers pull from, as it will
force needless merges on other developers to clean up the history.
+If you need to undo changes that you have pushed, use gitlink:git-revert[1]
+instead.
The git grep command can search for strings in any version of your
project, so