.\" 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\-CLONE" "1" "01/19/2007" "" ""
+.TH "GIT\-CLONE" "1" "02/20/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.nf
\fIgit\-clone\fR [\-\-template=<template_directory>] [\-l [\-s]] [\-q] [\-n] [\-\-bare]
[\-o <name>] [\-u <upload\-pack>] [\-\-reference <repository>]
- [\-\-depth=<depth>] <repository> [<directory>]
+ [\-\-depth <depth>] <repository> [<directory>]
.fi
.SH "DESCRIPTION"
Clones a repository into a newly created directory, creates remote\-tracking branches for each branch in the cloned repository (visible using git branch \-r), and creates and checks out an initial branch equal to the cloned repository's currently active branch.
\-\-template=<template_directory>
Specify the directory from which templates will be used; if unset the templates are taken from the installation defined default, typically /usr/share/git\-core/templates.
.TP
-\-\-depth=<depth>
+\-\-depth <depth>
Create a \fIshallow\fR clone with a history truncated to the specified number of revs. A shallow repository has number of limitations (you cannot clone or fetch from it, nor push from nor into it), but is adequate if you want to only look at near the tip of a large project with a long history, and would want to send in a fixes as patches.
.TP
<repository>
.\" 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\-CONFIG" "1" "02/13/2007" "" ""
+.TH "GIT\-CONFIG" "1" "02/20/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
pull.twohead
The default merge strategy to use when pulling a single branch.
.TP
+remote.fetch
+The list of remotes which are fetched by "git remote update". See \fBgit\-remote\fR(1).
+.TP
remote.<name>.url
The URL of a remote repository. See \fBgit\-fetch\fR(1) or \fBgit\-push\fR(1).
.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" "02/04/2007" "" ""
+.TH "GIT\-REMOTE" "1" "02/20/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
\fIgit\-remote\fR add <name> <url>
\fIgit\-remote\fR show <name>
\fIgit\-remote\fR prune <name>
+\fIgit\-remote\fR update
.fi
.SH "DESCRIPTION"
Manage the set of repositories ("remotes") whose branches you track.
.TP
\fIprune\fR
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>".
+.TP
+\fIupdate\fR
+Fetch updates for the remotes in the repository. By default all remotes are updated, but this can be configured via the configuration parameter \fIremote.fetch\fR. (See \fBgit\-config\fR(1)).
.SH "DISCUSSION"
The remote configuration is achieved using the remote.origin.url and remote.origin.fetch configuration variables. (See \fBgit\-config\fR(1)).
.SH "EXAMPLES"
.\" 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/18/2007" "" ""
+.TH "GIT" "7" "02/20/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)