only when the file exists. If this configuration
variable is set to true, missing "$GIT_DIR/logs/<ref>"
file is automatically created for branch heads.
-
- This information can be used to determine what commit
- was the tip of a branch "2 days ago".
-
- This value is true by default in a repository that has
- a working directory associated with it, and false by
- default in a bare repository.
++
+This information can be used to determine what commit
+was the tip of a branch "2 days ago".
++
+This value is true by default in a repository that has
+a working directory associated with it, and false by
+default in a bare repository.
core.repositoryFormatVersion::
Internal variable identifying the repository format and layout
<p>In addition to the above, as a short-hand, the name of a\r
file in <tt>$GIT_DIR/remotes</tt> directory can be given; the\r
named file should be in the following format:</p>\r
-<div class="literalblock">\r
+<div class="listingblock">\r
<div class="content">\r
<pre><tt>URL: one of the above URL format\r
Push: <refspec>\r
be specified for additional branch mappings.</p>\r
<p>Or, equivalently, in the <tt>$GIT_DIR/config</tt> (note the use\r
of <tt>fetch</tt> instead of <tt>Pull:</tt>):</p>\r
-<div class="literalblock">\r
+<div class="listingblock">\r
<div class="content">\r
-<pre><tt>url = <url>\r
-push = <refspec>\r
-fetch = <refspec></tt></pre>\r
+<pre><tt>[remote "<remote>"]\r
+ url = <url>\r
+ push = <refspec>\r
+ fetch = <refspec></tt></pre>\r
</div></div>\r
<p>The name of a file in <tt>$GIT_DIR/branches</tt> directory can be\r
specified as an older notation short-hand; the named\r
<tt>$GIT_DIR/branches/<remote></tt> file that stores a <url>\r
without the fragment is equivalent to have this in the\r
corresponding file in the <tt>$GIT_DIR/remotes/</tt> directory.</p>\r
-<div class="literalblock">\r
+<div class="listingblock">\r
<div class="content">\r
<pre><tt>URL: <url>\r
Pull: refs/heads/master:<remote></tt></pre>\r
</div></div>\r
<p>while having <tt><url>#<head></tt> is equivalent to</p>\r
-<div class="literalblock">\r
+<div class="listingblock">\r
<div class="content">\r
<pre><tt>URL: <url>\r
Pull: refs/heads/<head>:<remote></tt></pre>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 24-Oct-2006 05:43:59 UTC\r
+Last updated 31-Dec-2006 08:29:25 UTC\r
</div>\r
</div>\r
</body>\r
<p>In addition to the above, as a short-hand, the name of a\r
file in <tt>$GIT_DIR/remotes</tt> directory can be given; the\r
named file should be in the following format:</p>\r
-<div class="literalblock">\r
+<div class="listingblock">\r
<div class="content">\r
<pre><tt>URL: one of the above URL format\r
Push: <refspec>\r
be specified for additional branch mappings.</p>\r
<p>Or, equivalently, in the <tt>$GIT_DIR/config</tt> (note the use\r
of <tt>fetch</tt> instead of <tt>Pull:</tt>):</p>\r
-<div class="literalblock">\r
+<div class="listingblock">\r
<div class="content">\r
-<pre><tt>url = <url>\r
-push = <refspec>\r
-fetch = <refspec></tt></pre>\r
+<pre><tt>[remote "<remote>"]\r
+ url = <url>\r
+ push = <refspec>\r
+ fetch = <refspec></tt></pre>\r
</div></div>\r
<p>The name of a file in <tt>$GIT_DIR/branches</tt> directory can be\r
specified as an older notation short-hand; the named\r
<tt>$GIT_DIR/branches/<remote></tt> file that stores a <url>\r
without the fragment is equivalent to have this in the\r
corresponding file in the <tt>$GIT_DIR/remotes/</tt> directory.</p>\r
-<div class="literalblock">\r
+<div class="listingblock">\r
<div class="content">\r
<pre><tt>URL: <url>\r
Pull: refs/heads/master:<remote></tt></pre>\r
</div></div>\r
<p>while having <tt><url>#<head></tt> is equivalent to</p>\r
-<div class="literalblock">\r
+<div class="listingblock">\r
<div class="content">\r
<pre><tt>URL: <url>\r
Pull: refs/heads/<head>:<remote></tt></pre>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 29-Oct-2006 20:47:12 UTC\r
+Last updated 31-Dec-2006 08:29:26 UTC\r
</div>\r
</div>\r
</body>\r
<p>In addition to the above, as a short-hand, the name of a\r
file in <tt>$GIT_DIR/remotes</tt> directory can be given; the\r
named file should be in the following format:</p>\r
-<div class="literalblock">\r
+<div class="listingblock">\r
<div class="content">\r
<pre><tt>URL: one of the above URL format\r
Push: <refspec>\r
be specified for additional branch mappings.</p>\r
<p>Or, equivalently, in the <tt>$GIT_DIR/config</tt> (note the use\r
of <tt>fetch</tt> instead of <tt>Pull:</tt>):</p>\r
-<div class="literalblock">\r
+<div class="listingblock">\r
<div class="content">\r
-<pre><tt>url = <url>\r
-push = <refspec>\r
-fetch = <refspec></tt></pre>\r
+<pre><tt>[remote "<remote>"]\r
+ url = <url>\r
+ push = <refspec>\r
+ fetch = <refspec></tt></pre>\r
</div></div>\r
<p>The name of a file in <tt>$GIT_DIR/branches</tt> directory can be\r
specified as an older notation short-hand; the named\r
<tt>$GIT_DIR/branches/<remote></tt> file that stores a <url>\r
without the fragment is equivalent to have this in the\r
corresponding file in the <tt>$GIT_DIR/remotes/</tt> directory.</p>\r
-<div class="literalblock">\r
+<div class="listingblock">\r
<div class="content">\r
<pre><tt>URL: <url>\r
Pull: refs/heads/master:<remote></tt></pre>\r
</div></div>\r
<p>while having <tt><url>#<head></tt> is equivalent to</p>\r
-<div class="literalblock">\r
+<div class="listingblock">\r
<div class="content">\r
<pre><tt>URL: <url>\r
Pull: refs/heads/<head>:<remote></tt></pre>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 13-Dec-2006 10:14:07 UTC\r
+Last updated 31-Dec-2006 08:29:27 UTC\r
</div>\r
</div>\r
</body>\r
</dt>\r
<dd>\r
<p>\r
- git-repo-config will ensure that the output is a simple decimal number\r
+ git-repo-config will ensure that the output is a simple\r
+ decimal number. An optional value suffix of <em>k</em>, <em>m</em>, or <em>g</em>\r
+ in the config file will cause the value to be multiplied\r
+ by 1024, 1048576, or 1073741824 prior to output.\r
</p>\r
</dd>\r
</dl>\r
variable is set to true, missing "$GIT_DIR/logs/<ref>"\r
file is automatically created for branch heads.\r
</p>\r
-<div class="literalblock">\r
-<div class="content">\r
-<pre><tt>This information can be used to determine what commit\r
-was the tip of a branch "2 days ago".</tt></pre>\r
-</div></div>\r
-<div class="literalblock">\r
-<div class="content">\r
-<pre><tt>This value is true by default in a repository that has\r
+<p>This information can be used to determine what commit\r
+was the tip of a branch "2 days ago".</p>\r
+<p>This value is true by default in a repository that has\r
a working directory associated with it, and false by\r
-default in a bare repository.</tt></pre>\r
-</div></div>\r
+default in a bare repository.</p>\r
</dd>\r
<dt>\r
core.repositoryFormatVersion\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 29-Dec-2006 05:18:19 UTC\r
+Last updated 31-Dec-2006 08:29:27 UTC\r
</div>\r
</div>\r
</body>\r
git-repo-config will ensure that the output is "true" or "false"
--int::
- git-repo-config will ensure that the output is a simple decimal number
+ git-repo-config will ensure that the output is a simple
+ decimal number. An optional value suffix of 'k', 'm', or 'g'
+ in the config file will cause the value to be multiplied
+ by 1024, 1048576, or 1073741824 prior to output.
ENVIRONMENT
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>
+------------
+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
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
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>
+------------
+URL: <url>
+Pull: refs/heads/master:<remote>
+------------
+
while having `<url>#<head>` is equivalent to
- URL: <url>
- Pull: refs/heads/<head>:<remote>
+------------
+URL: <url>
+Pull: refs/heads/<head>:<remote>
+------------