.\" 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" "12/21/2006" "" ""
+.TH "GIT\-CLONE" "1" "01/01/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
No checkout of HEAD is performed after the clone is complete.
.TP
\-\-bare
-Make a \fIbare\fR GIT repository. That is, instead of creating <directory> and placing the administrative files in <directory>/.git, make the <directory> itself the $GIT_DIR. This obviously implies the \-n because there is nowhere to check out the working tree. Also the branch heads at the remote are copied directly to corresponding local branch heads, without mapping them to refs/remotes/origin/. When this option is used, neither the origin branch nor the default remotes/origin file is created.
+Make a \fIbare\fR GIT repository. That is, instead of creating <directory> and placing the administrative files in <directory>/.git, make the <directory> itself the $GIT_DIR. This obviously implies the \-n because there is nowhere to check out the working tree. Also the branch heads at the remote are copied directly to corresponding local branch heads, without mapping them to refs/remotes/origin/. When this option is used, neither remote\-tracking branches nor the related configuration variables are created.
.TP
\-\-origin <name> , \-o <name>
-Instead of using the branch name \fIorigin\fR to keep track of the upstream repository, use <name> instead. Note that the shorthand name stored in remotes/origin is not affected, but the local branch name to pull the remote master branch into is.
+Instead of using the remote name \fIorigin\fR to keep track of the upstream repository, use <name> instead.
.TP
\-\-upload\-pack <upload\-pack> , \-u <upload\-pack>
When given, and the repository to clone from is handled by \fIgit\-fetch\-pack\fR, \fI\-\-exec=<upload\-pack>\fR is passed to the command to specify non\-default path for the command run on the other end.
.\" 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\-FETCH" "1" "12/31/2006" "" ""
+.TH "GIT\-FETCH" "1" "01/01/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
In addition to the above, as a short\-hand, the name of a file in $GIT_DIR/remotes directory can be given; the named file should be in the following format:
.sp
.nf
-URL: one of the above URL format
-Push: <refspec>
-Pull: <refspec>
+ URL: one of the above URL format
+ Push: <refspec>
+ Pull: <refspec>
.fi
Then such a short\-hand is specified in place of <repository> without <refspec> parameters on the command line, <refspec> specified on Push: lines or Pull: lines are used for git\-push and git\-fetch/git\-pull, respectively. Multiple Push: and Pull: lines may be specified for additional branch mappings.
Or, equivalently, in the $GIT_DIR/config (note the use of fetch instead of Pull:):
.sp
.nf
-[remote "<remote>"]
- url = <url>
- push = <refspec>
- fetch = <refspec>
+ [remote "<remote>"]
+ url = <url>
+ push = <refspec>
+ fetch = <refspec>
.fi
The name of a file in $GIT_DIR/branches directory can be specified as an older notation short\-hand; the named file should contain a single line, a URL in one of the above formats, optionally followed by a hash # and the name of remote head (URL fragment notation). $GIT_DIR/branches/<remote> file that stores a <url> without the fragment is equivalent to have this in the corresponding file in the $GIT_DIR/remotes/ directory.
.sp
.nf
-URL: <url>
-Pull: refs/heads/master:<remote>
+ URL: <url>
+ Pull: refs/heads/master:<remote>
.fi
while having <url>#<head> is equivalent to
.sp
.nf
-URL: <url>
-Pull: refs/heads/<head>:<remote>
+ URL: <url>
+ Pull: refs/heads/<head>:<remote>
.fi
.SH "SEE ALSO"
\fBgit\-pull\fR(1)
.\" 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\-PULL" "1" "12/31/2006" "" ""
+.TH "GIT\-PULL" "1" "01/01/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
In addition to the above, as a short\-hand, the name of a file in $GIT_DIR/remotes directory can be given; the named file should be in the following format:
.sp
.nf
-URL: one of the above URL format
-Push: <refspec>
-Pull: <refspec>
+ URL: one of the above URL format
+ Push: <refspec>
+ Pull: <refspec>
.fi
Then such a short\-hand is specified in place of <repository> without <refspec> parameters on the command line, <refspec> specified on Push: lines or Pull: lines are used for git\-push and git\-fetch/git\-pull, respectively. Multiple Push: and Pull: lines may be specified for additional branch mappings.
Or, equivalently, in the $GIT_DIR/config (note the use of fetch instead of Pull:):
.sp
.nf
-[remote "<remote>"]
- url = <url>
- push = <refspec>
- fetch = <refspec>
+ [remote "<remote>"]
+ url = <url>
+ push = <refspec>
+ fetch = <refspec>
.fi
The name of a file in $GIT_DIR/branches directory can be specified as an older notation short\-hand; the named file should contain a single line, a URL in one of the above formats, optionally followed by a hash # and the name of remote head (URL fragment notation). $GIT_DIR/branches/<remote> file that stores a <url> without the fragment is equivalent to have this in the corresponding file in the $GIT_DIR/remotes/ directory.
.sp
.nf
-URL: <url>
-Pull: refs/heads/master:<remote>
+ URL: <url>
+ Pull: refs/heads/master:<remote>
.fi
while having <url>#<head> is equivalent to
.sp
.nf
-URL: <url>
-Pull: refs/heads/<head>:<remote>
+ URL: <url>
+ Pull: refs/heads/<head>:<remote>
.fi
.SH "MERGE STRATEGIES"
.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\-PUSH" "1" "12/31/2006" "" ""
+.TH "GIT\-PUSH" "1" "01/01/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
In addition to the above, as a short\-hand, the name of a file in $GIT_DIR/remotes directory can be given; the named file should be in the following format:
.sp
.nf
-URL: one of the above URL format
-Push: <refspec>
-Pull: <refspec>
+ URL: one of the above URL format
+ Push: <refspec>
+ Pull: <refspec>
.fi
Then such a short\-hand is specified in place of <repository> without <refspec> parameters on the command line, <refspec> specified on Push: lines or Pull: lines are used for git\-push and git\-fetch/git\-pull, respectively. Multiple Push: and Pull: lines may be specified for additional branch mappings.
Or, equivalently, in the $GIT_DIR/config (note the use of fetch instead of Pull:):
.sp
.nf
-[remote "<remote>"]
- url = <url>
- push = <refspec>
- fetch = <refspec>
+ [remote "<remote>"]
+ url = <url>
+ push = <refspec>
+ fetch = <refspec>
.fi
The name of a file in $GIT_DIR/branches directory can be specified as an older notation short\-hand; the named file should contain a single line, a URL in one of the above formats, optionally followed by a hash # and the name of remote head (URL fragment notation). $GIT_DIR/branches/<remote> file that stores a <url> without the fragment is equivalent to have this in the corresponding file in the $GIT_DIR/remotes/ directory.
.sp
.nf
-URL: <url>
-Pull: refs/heads/master:<remote>
+ URL: <url>
+ Pull: refs/heads/master:<remote>
.fi
while having <url>#<head> is equivalent to
.sp
.nf
-URL: <url>
-Pull: refs/heads/<head>:<remote>
+ URL: <url>
+ Pull: refs/heads/<head>:<remote>
.fi
.SH "AUTHOR"
Written by Junio C Hamano <junkio@cox.net>, later rewritten in C by Linus Torvalds <torvalds@osdl.org>
projects / git.git / commitdiff