Autogenerated HTML docs for v1.4.4.4-g9a5e4

diff --git a/config.txt b/config.txt
index 4318bf9334d22541b741b4be3fe0315f0e1480e9..b4aae0d0aeba86e995b37a5fe3ab7ec61e268687 100644 (file)
--- a/config.txt
+++ b/config.txt
@@ -118,6 +118,34 @@ core.legacyheaders::
        database directly (where the "http://" and "rsync://" protocols
        count as direct access).
 
+core.packedGitWindowSize::
+       Number of bytes of a pack file to map into memory in a
+       single mapping operation.  Larger window sizes may allow
+       your system to process a smaller number of large pack files
+       more quickly.  Smaller window sizes will negatively affect
+       performance due to increased calls to the operating system's
+       memory manager, but may improve performance when accessing
+       a large number of large pack files.
++
+Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
+MiB on 32 bit platforms and 1 GiB on 64 bit platforms.  This should
+be reasonable for all users/operating systems.  You probably do
+not need to adjust this value.
++
+Common unit suffixes of 'k', 'm', or 'g' are supported.
+
+core.packedGitLimit::
+       Maximum number of bytes to map simultaneously into memory
+       from pack files.  If Git needs to access more than this many
+       bytes at once to complete an operation it will unmap existing
+       regions to reclaim virtual address space within the process.
++
+Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
+This should be reasonable for all users/operating systems, except on
+the largest projects.  You probably do not need to adjust this value.
++
+Common unit suffixes of 'k', 'm', or 'g' are supported.
+
 alias.*::
        Command aliases for the gitlink:git[1] command wrapper - e.g.
        after defining "alias.last = cat-file commit HEAD", the invocation

diff --git a/everyday.html b/everyday.html
index c36c9357f1ab4d7927d05669a2160f35261c3648..bf4bbcd1d4444d8d48b7e974d025dc6314e55e33 100644 (file)
--- a/everyday.html
+++ b/everyday.html
@@ -284,7 +284,7 @@ of git repositories.</p>
 <ul>\r
 <li>\r
 <p>\r
-<a href="git-init-db.html">git-init-db(1)</a> or <a href="git-clone.html">git-clone(1)</a> to create a\r
+<a href="git-init.html">git-init(1)</a> or <a href="git-clone.html">git-clone(1)</a> to create a\r
     new repository.\r
 </p>\r
 </li>\r
@@ -440,7 +440,7 @@ Use a tarball as a starting point for a new repository.
 <div class="content">\r
 <pre><tt>$ tar zxf frotz.tar.gz\r
 $ cd frotz\r
-$ git-init-db\r
+$ git-init\r
 $ git add . <b>(1)</b>\r
 $ git commit -m 'import of frotz source tree.'\r
 $ git tag v2.43 <b>(2)</b></tt></pre>\r
@@ -1070,7 +1070,7 @@ upload to public HTTP server hosted by your ISP.
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 28-Dec-2006 00:59:31 UTC\r
+Last updated 08-Jan-2007 06:53:25 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/everyday.txt b/everyday.txt
index 2105a3d2e7337105263c8a9fef466609c63fc163..4e83994c588fc5f4853abc3839378281c58c9253 100644 (file)
--- a/everyday.txt
+++ b/everyday.txt
@@ -25,7 +25,7 @@ Basic Repository[[Basic Repository]]
 
 Everybody uses these commands to maintain git repositories.
 
-  * gitlink:git-init-db[1] or gitlink:git-clone[1] to create a
+  * gitlink:git-init[1] or gitlink:git-clone[1] to create a
     new repository.
 
   * gitlink:git-fsck-objects[1] to check the repository for errors.
@@ -107,7 +107,7 @@ Use a tarball as a starting point for a new repository.::
 ------------
 $ tar zxf frotz.tar.gz
 $ cd frotz
-$ git-init-db
+$ git-init
 $ git add . <1>
 $ git commit -m 'import of frotz source tree.'
 $ git tag v2.43 <2>

diff --git a/git-init-db.html b/git-init-db.html
index 5c79f9d5e6b271859af2c58ebcf4aae885ccbad9..a9aa49c55d62d22a149088446c59b401d7a05ab8 100644 (file)
--- a/git-init-db.html
+++ b/git-init-db.html
@@ -346,6 +346,7 @@ otherwise the default <tt>$GIT_DIR/objects</tt> directory is used.</p>
 <p>Running <tt>git-init-db</tt> in an existing repository is safe. It will not overwrite\r
 things that are already there. The primary reason for rerunning <tt>git-init-db</tt>\r
 is to pick up newly added templates.</p>\r
+<p>Note that <tt>git-init</tt> is the same as <tt>git-init-db</tt>.</p>\r
 </div>\r
 <h2>EXAMPLES</h2>\r
 <div class="sectionbody">\r
@@ -389,7 +390,7 @@ add all existing file to the index
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 03-Oct-2006 08:41:08 UTC\r
+Last updated 08-Jan-2007 06:53:18 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-init-db.txt b/git-init-db.txt
index ca7d09dc0a8563a1d8005bc83a89d19c785c1a3d..bc3ba14939054657bd82b8e3a8eb876e26ff14b0 100644 (file)
--- a/git-init-db.txt
+++ b/git-init-db.txt
@@ -74,6 +74,7 @@ Running `git-init-db` in an existing repository is safe. It will not overwrite
 things that are already there. The primary reason for rerunning `git-init-db`
 is to pick up newly added templates.
 
+Note that `git-init` is the same as `git-init-db`.
 
 
 EXAMPLES

diff --git a/git-repo-config.html b/git-repo-config.html
index 5510abecaf29f65ae0809399cf4e14dd13d3fa63..78ca7305cc7ea6d9ceebec0ee113a0cfa1e7256a 100644 (file)
--- a/git-repo-config.html
+++ b/git-repo-config.html
@@ -725,6 +725,40 @@ core.legacyheaders
 </p>\r
 </dd>\r
 <dt>\r
+core.packedGitWindowSize\r
+</dt>\r
+<dd>\r
+<p>\r
+        Number of bytes of a pack file to map into memory in a\r
+        single mapping operation.  Larger window sizes may allow\r
+        your system to process a smaller number of large pack files\r
+        more quickly.  Smaller window sizes will negatively affect\r
+        performance due to increased calls to the operating system's\r
+        memory manager, but may improve performance when accessing\r
+        a large number of large pack files.\r
+</p>\r
+<p>Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32\r
+MiB on 32 bit platforms and 1 GiB on 64 bit platforms.  This should\r
+be reasonable for all users/operating systems.  You probably do\r
+not need to adjust this value.</p>\r
+<p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p>\r
+</dd>\r
+<dt>\r
+core.packedGitLimit\r
+</dt>\r
+<dd>\r
+<p>\r
+        Maximum number of bytes to map simultaneously into memory\r
+        from pack files.  If Git needs to access more than this many\r
+        bytes at once to complete an operation it will unmap existing\r
+        regions to reclaim virtual address space within the process.\r
+</p>\r
+<p>Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.\r
+This should be reasonable for all users/operating systems, except on\r
+the largest projects.  You probably do not need to adjust this value.</p>\r
+<p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p>\r
+</dd>\r
+<dt>\r
 alias.*\r
 </dt>\r
 <dd>\r
@@ -1234,7 +1268,7 @@ receive.denyNonFastForwards
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 03-Jan-2007 22:02:02 UTC\r
+Last updated 08-Jan-2007 06:53:19 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-svn.html b/git-svn.html
index f92f5e27e04a163038aeb9d7309a1441d9599e80..6ac0965f5cff5e32ce3feb0b9f01720ff0e45694 100644 (file)
--- a/git-svn.html
+++ b/git-svn.html
@@ -459,6 +459,38 @@ manually joining branches on commit.</p>
 </p>\r
 </dd>\r
 <dt>\r
+-T&lt;trunk_subdir&gt;\r
+</dt>\r
+<dt>\r
+--trunk=&lt;trunk_subdir&gt;\r
+</dt>\r
+<dt>\r
+-t&lt;tags_subdir&gt;\r
+</dt>\r
+<dt>\r
+--tags=&lt;tags_subdir&gt;\r
+</dt>\r
+<dt>\r
+-b&lt;branches_subdir&gt;\r
+</dt>\r
+<dt>\r
+--branches=&lt;branches_subdir&gt;\r
+</dt>\r
+<dd>\r
+<p>\r
+        These are the command-line options for multi-init.  Each of\r
+        these flags can point to a relative repository path\r
+        (--tags=project/tags') or a full url\r
+        (--tags=https://foo.org/project/tags)\r
+</p>\r
+<p>--prefix=&lt;prefix&gt;\r
+        This allows one to specify a prefix which is prepended to the\r
+        names of remotes.  The prefix does not automatically include a\r
+        trailing slash, so be sure you include one in the argument if\r
+        that is what you want.  This is useful if you wish to track\r
+        multiple projects that share a common repository.</p>\r
+</dd>\r
+<dt>\r
 <em>multi-fetch</em>\r
 </dt>\r
 <dd>\r
@@ -930,7 +962,7 @@ detect them.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 07-Jan-2007 07:43:50 UTC\r
+Last updated 08-Jan-2007 06:53:20 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-svn.txt b/git-svn.txt
index ce63defffde85f4eb97d256417f78b5bc51365c6..8df43cb819770fe8540bc392bede53ba16070831 100644 (file)
--- a/git-svn.txt
+++ b/git-svn.txt
@@ -139,6 +139,24 @@ manually joining branches on commit.
        where the repository URL ends and where the repository path
        begins.
 
+-T<trunk_subdir>::
+--trunk=<trunk_subdir>::
+-t<tags_subdir>::
+--tags=<tags_subdir>::
+-b<branches_subdir>::
+--branches=<branches_subdir>::
+       These are the command-line options for multi-init.  Each of
+       these flags can point to a relative repository path
+       (--tags=project/tags') or a full url
+       (--tags=https://foo.org/project/tags)
+
+--prefix=<prefix>
+       This allows one to specify a prefix which is prepended to the
+       names of remotes.  The prefix does not automatically include a
+       trailing slash, so be sure you include one in the argument if
+       that is what you want.  This is useful if you wish to track
+       multiple projects that share a common repository.
+
 'multi-fetch'::
        This runs fetch on all known SVN branches we're tracking.  This
        will NOT discover new branches (unlike git-svnimport), so

diff --git a/git.html b/git.html
index ecdbbca6729ebe25283cd5c56737d9b9121127a6..bbc3ec0d80c630e1c2ebb617a4acee48e59f6f12 100644 (file)
--- a/git.html
+++ b/git.html
@@ -1044,6 +1044,9 @@ repositories.</p>
 </p>\r
 </dd>\r
 <dt>\r
+<a href="git-init.html">git-init(1)</a>\r
+</dt>\r
+<dt>\r
 <a href="git-init-db.html">git-init-db(1)</a>\r
 </dt>\r
 <dd>\r
@@ -2285,7 +2288,7 @@ contributors on the git-list &lt;git@vger.kernel.org&gt;.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 28-Dec-2006 00:59:29 UTC\r
+Last updated 08-Jan-2007 06:53:21 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git.txt b/git.txt
index 36b2126d847bf86f9efe5bdb1ce88acef9046633..5662cdc27cb35786e72dcf9c0db74009a3cba4aa 100644 (file)
--- a/git.txt
+++ b/git.txt
@@ -353,6 +353,7 @@ gitlink:git-hash-object[1]::
 gitlink:git-index-pack[1]::
        Build pack idx file for an existing packed archive.
 
+gitlink:git-init[1]::
 gitlink:git-init-db[1]::
        Creates an empty git object database, or reinitialize an
        existing one.

diff --git a/glossary.html b/glossary.html
index d77cbe1c945ef4c8c334184f8a5b3ed49a6bb210..e3f8f2189df939eb84f83935bde58e54a4c8c9ae 100644 (file)
--- a/glossary.html
+++ b/glossary.html
@@ -759,9 +759,12 @@ div.exampleblock-content {
 </dt>\r
 <dd>\r
 <p>\r
-        An <a href="#ref_object">object</a> is <a href="#ref_reachable">reachable</a> from a\r
-        <a href="#ref_ref">ref</a>/<a href="#ref_commit">commit</a>/<a href="#ref_tree">tree</a>/<a href="#ref_tag">tag</a>,\r
-        if there is a <a href="#ref_chain">chain</a> leading from the latter to the former.\r
+        All of the ancestors of a given <a href="#ref_commit">commit</a> are said to be\r
+        <a href="#ref_reachable">reachable</a> from that <a href="#ref_commit">commit</a>. More\r
+        generally, one <a href="#ref_object">object</a> is <a href="#ref_reachable">reachable</a> from\r
+        another if we can reach the one from the other by a <a href="#ref_chain">chain</a>\r
+        that follows tags to whatever they <a href="#ref_tag">tag</a>, commits to their\r
+        parents or trees, and trees to the trees or blobs that they contain.\r
 </p>\r
 </dd>\r
 <dt>\r
@@ -981,7 +984,7 @@ the git-list &lt;git@vger.kernel.org&gt;.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 01-Jan-2007 03:20:17 UTC\r
+Last updated 08-Jan-2007 06:53:26 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/glossary.txt b/glossary.txt
index 7c1a6592c112a76c23c2833537a13f40337c261c..cd61aa26065ba6f3d06df7d1c00e2e81d42bce9e 100644 (file)
--- a/glossary.txt
+++ b/glossary.txt
@@ -235,8 +235,11 @@ push::
        local head, the push fails.
 
 reachable::
-       An object is reachable from a ref/commit/tree/tag, if there is a
-       chain leading from the latter to the former.
+       All of the ancestors of a given commit are said to be reachable from
+       that commit.  More generally, one object is reachable from another if
+       we can reach the one from the other by a chain that follows tags to
+       whatever they tag, commits to their parents or trees, and trees to the
+       trees or blobs that they contain.
 
 rebase::
        To clean a branch by starting from the head of the main line of

diff --git a/tutorial-2.html b/tutorial-2.html
index a18536c953a4d6159863b761fc0eb2ad451d2c32..5b4102f94ea61427fcfb6a4735e93f82e1e060e3 100644 (file)
--- a/tutorial-2.html
+++ b/tutorial-2.html
@@ -278,7 +278,7 @@ of the git documentation.</p>
 <div class="content">\r
 <pre><tt>$ mkdir test-project\r
 $ cd test-project\r
-$ git init-db\r
+$ git init\r
 Initialized empty Git repository in .git/\r
 $ echo 'hello world' &gt; file.txt\r
 $ git add .\r
@@ -646,7 +646,7 @@ example, creating a new commit.</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 16-Dec-2006 07:43:54 UTC\r
+Last updated 08-Jan-2007 06:53:24 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/tutorial-2.txt b/tutorial-2.txt
index 60e54777dc6cef259a045512f42a50527f430fb9..f48894c9a25001374210fba3f6782ccec996a664 100644 (file)
--- a/tutorial-2.txt
+++ b/tutorial-2.txt
@@ -17,7 +17,7 @@ Let's start a new project and create a small amount of history:
 ------------------------------------------------
 $ mkdir test-project
 $ cd test-project
-$ git init-db
+$ git init
 Initialized empty Git repository in .git/
 $ echo 'hello world' > file.txt
 $ git add .

diff --git a/tutorial.html b/tutorial.html
index 66b00fc72dee3052b38187037b7cee6a13739fb5..d88def37e4db87801131425ae37e63916b34cf70 100644 (file)
--- a/tutorial.html
+++ b/tutorial.html
@@ -291,7 +291,7 @@ can place it under git revision control as follows.</p>
 <div class="content">\r
 <pre><tt>$ tar xzf project.tar.gz\r
 $ cd project\r
-$ git init-db</tt></pre>\r
+$ git init</tt></pre>\r
 </div></div>\r
 <p>Git will reply</p>\r
 <div class="listingblock">\r
@@ -785,7 +785,7 @@ digressions that may be interesting at this point are:</p>
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 07-Jan-2007 07:43:51 UTC\r
+Last updated 08-Jan-2007 06:53:23 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/tutorial.txt b/tutorial.txt
index 01d4a47a97fa864c6948b8ae98ece1f00b1003da..d2bf0b905aa3f2b67f781310b9f60c05fa948c67 100644 (file)
--- a/tutorial.txt
+++ b/tutorial.txt
@@ -32,7 +32,7 @@ can place it under git revision control as follows.
 ------------------------------------------------
 $ tar xzf project.tar.gz
 $ cd project
-$ git init-db
+$ git init
 ------------------------------------------------
 
 Git will reply