.\" 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\-CHECKOUT" "1" "02/01/2007" "" ""
+.TH "GIT\-CHECKOUT" "1" "02/02/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.SH "SYNOPSIS"
.sp
.nf
-\fIgit\-checkout\fR [\-f] [\-b <new_branch> [\-l]] [\-m] [<branch>]
+\fIgit\-checkout\fR [\-q] [\-f] [\-b <new_branch> [\-l]] [\-m] [<branch>]
\fIgit\-checkout\fR [<tree\-ish>] <paths>\&...
.fi
.SH "DESCRIPTION"
When <paths> are given, this command does \fBnot\fR switch branches. It updates the named paths in the working tree from the index file (i.e. it runs git\-checkout\-index \-f \-u), or a named commit. In this case, \-f and \-b options are meaningless and giving either of them results in an error. <tree\-ish> argument can be used to specify a specific tree\-ish (i.e. commit, tag or tree) to update the index for the given paths before updating the working tree.
.SH "OPTIONS"
.TP
+\-q
+Quiet, supress feedback messages.
+.TP
\-f
Force a re\-read of everything.
.TP
.\" 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\-REMOTE" "1" "01/29/2007" "" ""
+.TH "GIT\-REMOTE" "1" "02/02/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
\fIgit\-remote\fR
\fIgit\-remote\fR add <name> <url>
\fIgit\-remote\fR show <name>
+\fIgit\-remote\fR prune <name>
.fi
.SH "DESCRIPTION"
Manage the set of repositories ("remotes") whose branches you track.
In the third form, gives some information about the remote <name>.
+In the fourth form, deletes all stale tracking branches under <name>. These stale branches have already been removed from the remote repository referenced by <name>, but are still locally available in "remotes/<name>".
+
The remote configuration is achieved using the remote.origin.url and remote.origin.fetch configuration variables. (See \fBgit\-config\fR(1)).
.SH "EXAMPLES"
Add a new remote, fetch, and check out a branch from it:
.\" 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\-REV\-PARSE" "1" "01/18/2007" "" ""
+.TH "GIT\-REV\-PARSE" "1" "02/02/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
A ref followed by the suffix \fI@\fR with an ordinal specification enclosed in a brace pair (e.g. \fI{1}\fR, \fI{15}\fR) to specify the n\-th prior value of that ref. For example \fImaster@{1}\fR is the immediate prior value of \fImaster\fR while \fImaster@{5}\fR is the 5th prior value of \fImaster\fR. This suffix may only be used immediately following a ref name and the ref must have an existing log ($GIT_DIR/logs/<ref>).
.TP
\(bu
+You can use the \fI@\fR construct with an empty ref part to get at a reflog of the current branch. For example, if you are on the branch \fIblabla\fR, then \fI@{1}\fR means the same as \fIblabla@{1}\fR.
+.TP
+\(bu
A suffix \fI^\fR to a revision parameter means the first parent of that commit object. \fI^<n>\fR means the <n>th parent (i.e. \fIrev^\fR is equivalent to \fIrev^1\fR). As a special rule, \fIrev^0\fR means the commit itself and is used when \fIrev\fR is the object name of a tag object that refers to a commit object.
.TP
\(bu
.\" 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/01/2007" "" ""
+.TH "GIT" "7" "02/02/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)