.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-SHOW\-BRANCH" "1" "01/25/2007" "" ""
+.TH "GIT\-SHOW\-BRANCH" "1" "02/05/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
\fIgit\-show\-branch\fR [\-\-all] [\-\-remotes] [\-\-topo\-order] [\-\-current]
[\-\-more=<n> | \-\-list | \-\-independent | \-\-merge\-base]
[\-\-no\-name | \-\-sha1\-name] [\-\-topics] [<rev> | <glob>]\&...
-\fIgit\-show\-branch\fR (\-g|\-\-reflog)[=<n>[,<base>]] [\-\-list] <ref>
+\fIgit\-show\-branch\fR (\-g|\-\-reflog)[=<n>[,<base>]] [\-\-list] [<ref>]
.fi
.SH "DESCRIPTION"
Shows the commit ancestry graph starting from the commits named with <rev>s or <globs>s (or all refs under $GIT_DIR/refs/heads and/or $GIT_DIR/refs/tags) semi\-visually.
\-\-topics
Shows only commits that are NOT on the first branch given. This helps track topic branches by hiding any commit that is already in the main line of development. When given "git show\-branch \-\-topics master topic1 topic2", this will show the revisions given by "git rev\-list ^master topic1 topic2"
.TP
-\-\-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.
+\-\-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. 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.
.SH "OUTPUT"
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-SYMBOLIC\-REF" "1" "01/19/2007" "" ""
+.TH "GIT\-SYMBOLIC\-REF" "1" "02/05/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.SH "NAME"
git\-symbolic\-ref \- Read and modify symbolic refs
.SH "SYNOPSIS"
-\fIgit\-symbolic\-ref\fR [\-q] <name> [<ref>]
+\fIgit\-symbolic\-ref\fR [\-q] [\-m <reason>] <name> [<ref>]
.SH "DESCRIPTION"
Given one argument, reads which branch head the given symbolic ref refers to and outputs its path, relative to the .git/ directory. Typically you would give HEAD as the <name> argument to see on which branch your working tree is on.
.TP
\-q
Do not issue an error message if the <name> is not a symbolic ref but a detached HEAD; instead exit with non\-zero status silently.
+.TP
+\-m
+Update the reflog for <name> with <reason>. This is valid only when creating or updating a symbolic ref.
.SH "NOTES"
In the past, .git/HEAD was a symbolic link pointing at refs/heads/master. When we wanted to switch to another branch, we did ln \-sf refs/heads/newbranch .git/HEAD, and when we wanted to find out which branch we are on, we did readlink .git/HEAD. This was fine, and internally that is what still happens by default, but on platforms that do not have working symlinks, or that do not have the readlink(1) command, this was a bit cumbersome. On some platforms, ln \-sf does not even work as advertised (horrors). Therefore symbolic links are now deprecated and symbolic refs are used by default.
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT" "7" "02/04/2007" "" ""
+.TH "GIT" "7" "02/05/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)