existing contents of `.git/FETCH_HEAD`. Without this
option old data in `.git/FETCH_HEAD` will be overwritten.
+--upload-pack <upload-pack>::
+-u <upload-pack>::
+ When given, and the repository to fetch from is handled
+ by 'git-fetch-pack', '--exec=<upload-pack>' is passed to
+ the command to specify non-default path for the command
+ run on the other end.
+
-f, \--force::
When `git-fetch` is used with `<rbranch>:<lbranch>`
refspec, it refuses to update the local branch
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
<div class="verseblock">\r
-<div class="content"><em>git-clone</em> [-l [-s]] [-q] [-n] [--naked] [-o <name>] [-u <upload-pack>]\r
+<div class="content"><em>git-clone</em> [-l [-s]] [-q] [-n] [--bare] [-o <name>] [-u <upload-pack>]\r
<repository> [<directory>]</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
</p>\r
</dd>\r
<dt>\r
---naked\r
+--bare\r
</dt>\r
<dd>\r
<p>\r
- Make a <em>naked</em> GIT repository. That is, instead of\r
+ Make a <em>bare</em> GIT repository. That is, instead of\r
creating <tt><directory></tt> and placing the administrative\r
files in <tt><directory>/.git</tt>, make the <tt><directory></tt>\r
- itself the <tt>$GIT_DIR</tt>. This implies <tt>-n</tt> option.\r
+ itself the <tt>$GIT_DIR</tt>. This implies <tt>-n</tt> option. When\r
+ this option is used, neither the <tt>origin</tt> branch nor the\r
+ default <tt>remotes/origin</tt> file is created.\r
</p>\r
</dd>\r
<dt>\r
</div></div>\r
</dd>\r
<dt>\r
-Create a naked repository to publish your changes to the public\r
+Create a bare repository to publish your changes to the public\r
</dt>\r
<dd>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>$ git clone --naked -l /home/proj/.git /pub/scm/proj.git</tt></pre>\r
+<pre><tt>$ git clone --bare -l /home/proj/.git /pub/scm/proj.git</tt></pre>\r
</div></div>\r
</dd>\r
<dt>\r
<dd>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>$ git clone --naked -l -s /pub/scm/.../torvalds/linux-2.6.git \\r
+<pre><tt>$ git clone --bare -l -s /pub/scm/.../torvalds/linux-2.6.git \\r
/pub/scm/.../me/subsys-2.6.git</tt></pre>\r
</div></div>\r
</dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 15-Jan-2006 02:13:28 PDT\r
+Last updated 25-Jan-2006 04:37:11 PDT\r
</div>\r
</div>\r
</body>\r
SYNOPSIS
--------
[verse]
-'git-clone' [-l [-s]] [-q] [-n] [--naked] [-o <name>] [-u <upload-pack>]
+'git-clone' [-l [-s]] [-q] [-n] [--bare] [-o <name>] [-u <upload-pack>]
<repository> [<directory>]
DESCRIPTION
-n::
No checkout of HEAD is performed after the clone is complete.
---naked::
- Make a 'naked' GIT repository. That is, instead of
+--bare::
+ Make a 'bare' GIT repository. That is, instead of
creating `<directory>` and placing the administrative
files in `<directory>/.git`, make the `<directory>`
- itself the `$GIT_DIR`. This implies `-n` option.
+ itself the `$GIT_DIR`. This implies `-n` option. When
+ this option is used, neither the `origin` branch nor the
+ default `remotes/origin` file is created.
-o <name>::
Instead of using the branch name 'origin' to keep track
------------
-Create a naked repository to publish your changes to the public::
+Create a bare repository to publish your changes to the public::
+
------------
-$ git clone --naked -l /home/proj/.git /pub/scm/proj.git
+$ git clone --bare -l /home/proj/.git /pub/scm/proj.git
------------
Create a repository on the kernel.org machine that borrows from Linus::
+
------------
-$ git clone --naked -l -s /pub/scm/.../torvalds/linux-2.6.git \
+$ git clone --bare -l -s /pub/scm/.../torvalds/linux-2.6.git \
/pub/scm/.../me/subsys-2.6.git
------------
</p>\r
</dd>\r
<dt>\r
+--upload-pack <upload-pack>\r
+</dt>\r
+<dt>\r
+-u <upload-pack>\r
+</dt>\r
+<dd>\r
+<p>\r
+ When given, and the repository to fetch from is handled\r
+ by <em>git-fetch-pack</em>, <em>--exec=<upload-pack></em> is passed to\r
+ the command to specify non-default path for the command\r
+ run on the other end.\r
+</p>\r
+</dd>\r
+<dt>\r
-f, --force\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 13-Jan-2006 19:58:27 PDT\r
+Last updated 25-Jan-2006 04:37:11 PDT\r
</div>\r
</div>\r
</body>\r
</p>\r
</dd>\r
<dt>\r
+--upload-pack <upload-pack>\r
+</dt>\r
+<dt>\r
+-u <upload-pack>\r
+</dt>\r
+<dd>\r
+<p>\r
+ When given, and the repository to fetch from is handled\r
+ by <em>git-fetch-pack</em>, <em>--exec=<upload-pack></em> is passed to\r
+ the command to specify non-default path for the command\r
+ run on the other end.\r
+</p>\r
+</dd>\r
+<dt>\r
-f, --force\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 13-Jan-2006 19:58:28 PDT\r
+Last updated 25-Jan-2006 04:37:12 PDT\r
</div>\r
</div>\r
</body>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 22-Jan-2006 23:54:19 PDT\r
+Last updated 25-Jan-2006 04:37:14 PDT\r
</div>\r
</div>\r
</body>\r
Discussion[[Discussion]]
------------------------
-include::../README[]
+include::README[]
Authors
-------
<div class="sectionbody">\r
<p>You may find these things in your git repository (<tt>.git</tt>\r
directory for a repository associated with your working tree, or\r
-<tt><em>project</em>.git</tt> directory for a public <em>naked</em> repository).</p>\r
+<tt><em>project</em>.git</tt> directory for a public <em>bare</em> repository).</p>\r
<dl>\r
<dt>\r
objects\r
A symlink of the form <tt>refs/heads/<em>name</em></tt> to point at\r
the current branch, if exists. It does not mean much if\r
the repository is not associated with any working tree\r
- (i.e. <em>naked</em> repository), but a valid git repository\r
+ (i.e. a <em>bare</em> repository), but a valid git repository\r
<strong>must</strong> have such a symlink here. It is legal if the\r
named branch <em>name</em> does not (yet) exist.\r
</p>\r
<dd>\r
<p>\r
The current index file for the repository. It is\r
- usually not found in a naked repository.\r
+ usually not found in a bare repository.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 06-Jan-2006 17:12:59 PDT\r
+Last updated 25-Jan-2006 04:37:17 PDT\r
</div>\r
</div>\r
</body>\r
You may find these things in your git repository (`.git`
directory for a repository associated with your working tree, or
-`'project'.git` directory for a public 'naked' repository).
+`'project'.git` directory for a public 'bare' repository).
objects::
Object store associated with this repository. Usually
A symlink of the form `refs/heads/'name'` to point at
the current branch, if exists. It does not mean much if
the repository is not associated with any working tree
- (i.e. 'naked' repository), but a valid git repository
+ (i.e. a 'bare' repository), but a valid git repository
*must* have such a symlink here. It is legal if the
named branch 'name' does not (yet) exist.
index::
The current index file for the repository. It is
- usually not found in a naked repository.
+ usually not found in a bare repository.
info::
Additional information about the repository is recorded