</dt>\r
<dd>\r
<p>\r
- The (possibly remote) repository to clone from. It can\r
- be any URL git-fetch supports.\r
+ The (possibly remote) repository to clone from. See the\r
+ <a href="#URLS">URLS</a> section below for more information on specifying\r
+ repositories.\r
</p>\r
</dd>\r
<dt>\r
</dd>\r
</dl>\r
</div>\r
+<h2>GIT URLS<a id="URLS"></a></h2>\r
+<div class="sectionbody">\r
+<p>One of the following notations can be used\r
+to name the remote repository:</p>\r
+<div class="exampleblock">\r
+<div class="exampleblock-content">\r
+<ul>\r
+<li>\r
+<p>\r
+rsync://host.xz/path/to/repo.git/\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+http://host.xz/path/to/repo.git/\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+https://host.xz/path/to/repo.git/\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+git://host.xz/path/to/repo.git/\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+git://host.xz/~user/path/to/repo.git/\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+ssh://[user@]host.xz/path/to/repo.git/\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+ssh://[user@]host.xz/~user/path/to/repo.git/\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+ssh://[user@]host.xz/~/path/to/repo.git\r
+</p>\r
+</li>\r
+</ul>\r
+</div></div>\r
+<p>SSH is the default transport protocol. You can optionally specify\r
+which user to log-in as, and an alternate, scp-like syntax is also\r
+supported. Both syntaxes support username expansion,\r
+as does the native git protocol. The following three are\r
+identical to the last three above, respectively:</p>\r
+<div class="exampleblock">\r
+<div class="exampleblock-content">\r
+<ul>\r
+<li>\r
+<p>\r
+[user@]host.xz:/path/to/repo.git/\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+[user@]host.xz:~user/path/to/repo.git/\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+[user@]host.xz:path/to/repo.git\r
+</p>\r
+</li>\r
+</ul>\r
+</div></div>\r
+<p>To sync with a local directory, use:</p>\r
+<div class="exampleblock">\r
+<div class="exampleblock-content">\r
+<ul>\r
+<li>\r
+<p>\r
+/path/to/repo.git/\r
+</p>\r
+</li>\r
+</ul>\r
+</div></div>\r
+</div>\r
<h2>Examples</h2>\r
<div class="sectionbody">\r
<dl>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Jun-2007 09:48:57 UTC\r
+Last updated 06-Jul-2007 17:01:29 UTC\r
</div>\r
</div>\r
</body>\r
as patches.
<repository>::
- The (possibly remote) repository to clone from. It can
- be any URL git-fetch supports.
+ The (possibly remote) repository to clone from. See the
+ <<URLS,URLS>> section below for more information on specifying
+ repositories.
<directory>::
The name of a new directory to clone into. The "humanish"
for "host.xz:foo/.git"). Cloning into an existing directory
is not allowed.
+include::urls.txt[]
+
Examples
--------
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Jun-2007 09:49:04 UTC\r
+Last updated 06-Jul-2007 17:01:29 UTC\r
</div>\r
</div>\r
</body>\r
include::pull-fetch-param.txt[]
-include::urls.txt[]
+include::urls-remotes.txt[]
SEE ALSO
--------
tmpfs. Reportedly the speedup is very noticeable.</p>\r
<h3>Filters</h3>\r
<p>The filters are applied in the order as listed below. The <command>\r
-argument is always evaluated in shell using the <em>eval</em> command.\r
+argument is always evaluated in shell using the <em>eval</em> command (with the\r
+notable exception of the commit filter, for technical reasons).\r
Prior to that, the $GIT_COMMIT environment variable will be set to contain\r
the id of the commit being rewritten. Also, GIT_AUTHOR_NAME,\r
GIT_AUTHOR_EMAIL, GIT_AUTHOR_DATE, GIT_COMMITTER_NAME, GIT_COMMITTER_EMAIL,\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 05-Jul-2007 05:51:15 UTC\r
+Last updated 06-Jul-2007 17:01:30 UTC\r
</div>\r
</div>\r
</body>\r
~~~~~~~
The filters are applied in the order as listed below. The <command>
-argument is always evaluated in shell using the 'eval' command.
+argument is always evaluated in shell using the 'eval' command (with the
+notable exception of the commit filter, for technical reasons).
Prior to that, the $GIT_COMMIT environment variable will be set to contain
the id of the commit being rewritten. Also, GIT_AUTHOR_NAME,
GIT_AUTHOR_EMAIL, GIT_AUTHOR_DATE, GIT_COMMITTER_NAME, GIT_COMMITTER_EMAIL,
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Jun-2007 09:49:15 UTC\r
+Last updated 06-Jul-2007 17:01:31 UTC\r
</div>\r
</div>\r
</body>\r
include::pull-fetch-param.txt[]
-include::urls.txt[]
+include::urls-remotes.txt[]
include::merge-strategies.txt[]
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Jun-2007 09:49:16 UTC\r
+Last updated 06-Jul-2007 17:01:31 UTC\r
</div>\r
</div>\r
</body>\r
-v::
Run verbosely.
-include::urls.txt[]
+include::urls-remotes.txt[]
Examples
<div class="listingblock">\r
<div class="content">\r
<pre><tt>$ git config --get remote.origin.url\r
-/home/bob/myrepo</tt></pre>\r
+/home/alice/project</tt></pre>\r
</div></div>\r
<p>(The complete configuration created by git-clone is visible using\r
"git config -l", and the <a href="git-config.html">git-config(1)</a> man page\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 16-Jun-2007 09:49:28 UTC\r
+Last updated 06-Jul-2007 17:01:32 UTC\r
</div>\r
</div>\r
</body>\r
-------------------------------------
$ git config --get remote.origin.url
-/home/bob/myrepo
+/home/alice/project
-------------------------------------
(The complete configuration created by git-clone is visible using
--- /dev/null
+include::urls.txt[]
+
+REMOTES
+-------
+
+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:
+
+------------
+ URL: one of the above URL format
+ Push: <refspec>
+ Pull: <refspec>
+
+------------
+
+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:`):
+
+------------
+ [remote "<remote>"]
+ url = <url>
+ push = <refspec>
+ fetch = <refspec>
+
+------------
+
+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.
+
+------------
+ URL: <url>
+ Pull: refs/heads/master:<remote>
+
+------------
+
+while having `<url>#<head>` is equivalent to
+
+------------
+ URL: <url>
+ Pull: refs/heads/<head>:<remote>
+------------
===============================================================
- /path/to/repo.git/
===============================================================
-
-REMOTES
--------
-
-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:
-
-------------
- URL: one of the above URL format
- Push: <refspec>
- Pull: <refspec>
-
-------------
-
-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:`):
-
-------------
- [remote "<remote>"]
- url = <url>
- push = <refspec>
- fetch = <refspec>
-
-------------
-
-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.
-
-------------
- URL: <url>
- Pull: refs/heads/master:<remote>
-
-------------
-
-while having `<url>#<head>` is equivalent to
-
-------------
- URL: <url>
- Pull: refs/heads/<head>:<remote>
-------------
projects / git.git / commitdiff