From: Junio C Hamano <junio@hera.kernel.org>
Date: Mon, 8 Jan 2007 06:53:32 +0000 (+0000)
Subject: Autogenerated HTML docs for v1.4.4.4-g9a5e4
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=fc4d38ced802738c5d6aaabf66a345d2d6c97c82;p=git.git

Autogenerated HTML docs for v1.4.4.4-g9a5e4
---

diff --git a/config.txt b/config.txt
index 4318bf933..b4aae0d0a 100644
--- 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 c36c9357f..bf4bbcd1d 100644
--- a/everyday.html
+++ b/everyday.html
@@ -284,7 +284,7 @@ of git repositories.</p>
 <ul>
 <li>
 <p>
-<a href="git-init-db.html">git-init-db(1)</a> or <a href="git-clone.html">git-clone(1)</a> to create a
+<a href="git-init.html">git-init(1)</a> or <a href="git-clone.html">git-clone(1)</a> to create a
     new repository.
 </p>
 </li>
@@ -440,7 +440,7 @@ Use a tarball as a starting point for a new repository.
 <div class="content">
 <pre><tt>$ tar zxf frotz.tar.gz
 $ cd frotz
-$ git-init-db
+$ git-init
 $ git add . <b>(1)</b>
 $ git commit -m 'import of frotz source tree.'
 $ git tag v2.43 <b>(2)</b></tt></pre>
@@ -1070,7 +1070,7 @@ upload to public HTTP server hosted by your ISP.
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 28-Dec-2006 00:59:31 UTC
+Last updated 08-Jan-2007 06:53:25 UTC
 </div>
 </div>
 </body>
diff --git a/everyday.txt b/everyday.txt
index 2105a3d2e..4e83994c5 100644
--- 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 5c79f9d5e..a9aa49c55 100644
--- 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
 things that are already there. The primary reason for rerunning <tt>git-init-db</tt>
 is to pick up newly added templates.</p>
+<p>Note that <tt>git-init</tt> is the same as <tt>git-init-db</tt>.</p>
 </div>
 <h2>EXAMPLES</h2>
 <div class="sectionbody">
@@ -389,7 +390,7 @@ add all existing file to the index
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 03-Oct-2006 08:41:08 UTC
+Last updated 08-Jan-2007 06:53:18 UTC
 </div>
 </div>
 </body>
diff --git a/git-init-db.txt b/git-init-db.txt
index ca7d09dc0..bc3ba1493 100644
--- 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 5510abeca..78ca7305c 100644
--- a/git-repo-config.html
+++ b/git-repo-config.html
@@ -725,6 +725,40 @@ core.legacyheaders
 </p>
 </dd>
 <dt>
+core.packedGitWindowSize
+</dt>
+<dd>
+<p>
+        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.
+</p>
+<p>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.</p>
+<p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p>
+</dd>
+<dt>
+core.packedGitLimit
+</dt>
+<dd>
+<p>
+        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.
+</p>
+<p>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.</p>
+<p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p>
+</dd>
+<dt>
 alias.*
 </dt>
 <dd>
@@ -1234,7 +1268,7 @@ receive.denyNonFastForwards
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 03-Jan-2007 22:02:02 UTC
+Last updated 08-Jan-2007 06:53:19 UTC
 </div>
 </div>
 </body>
diff --git a/git-svn.html b/git-svn.html
index f92f5e27e..6ac0965f5 100644
--- a/git-svn.html
+++ b/git-svn.html
@@ -459,6 +459,38 @@ manually joining branches on commit.</p>
 </p>
 </dd>
 <dt>
+-T&lt;trunk_subdir&gt;
+</dt>
+<dt>
+--trunk=&lt;trunk_subdir&gt;
+</dt>
+<dt>
+-t&lt;tags_subdir&gt;
+</dt>
+<dt>
+--tags=&lt;tags_subdir&gt;
+</dt>
+<dt>
+-b&lt;branches_subdir&gt;
+</dt>
+<dt>
+--branches=&lt;branches_subdir&gt;
+</dt>
+<dd>
+<p>
+        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)
+</p>
+<p>--prefix=&lt;prefix&gt;
+        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.</p>
+</dd>
+<dt>
 <em>multi-fetch</em>
 </dt>
 <dd>
@@ -930,7 +962,7 @@ detect them.</p>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 07-Jan-2007 07:43:50 UTC
+Last updated 08-Jan-2007 06:53:20 UTC
 </div>
 </div>
 </body>
diff --git a/git-svn.txt b/git-svn.txt
index ce63defff..8df43cb81 100644
--- 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 ecdbbca67..bbc3ec0d8 100644
--- a/git.html
+++ b/git.html
@@ -1044,6 +1044,9 @@ repositories.</p>
 </p>
 </dd>
 <dt>
+<a href="git-init.html">git-init(1)</a>
+</dt>
+<dt>
 <a href="git-init-db.html">git-init-db(1)</a>
 </dt>
 <dd>
@@ -2285,7 +2288,7 @@ contributors on the git-list &lt;git@vger.kernel.org&gt;.</p>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 28-Dec-2006 00:59:29 UTC
+Last updated 08-Jan-2007 06:53:21 UTC
 </div>
 </div>
 </body>
diff --git a/git.txt b/git.txt
index 36b2126d8..5662cdc27 100644
--- 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 d77cbe1c9..e3f8f2189 100644
--- a/glossary.html
+++ b/glossary.html
@@ -759,9 +759,12 @@ div.exampleblock-content {
 </dt>
 <dd>
 <p>
-        An <a href="#ref_object">object</a> is <a href="#ref_reachable">reachable</a> from a
-        <a href="#ref_ref">ref</a>/<a href="#ref_commit">commit</a>/<a href="#ref_tree">tree</a>/<a href="#ref_tag">tag</a>,
-        if there is a <a href="#ref_chain">chain</a> leading from the latter to the former.
+        All of the ancestors of a given <a href="#ref_commit">commit</a> are said to be
+        <a href="#ref_reachable">reachable</a> from that <a href="#ref_commit">commit</a>. More
+        generally, one <a href="#ref_object">object</a> is <a href="#ref_reachable">reachable</a> from
+        another if we can reach the one from the other by a <a href="#ref_chain">chain</a>
+        that follows tags to whatever they <a href="#ref_tag">tag</a>, commits to their
+        parents or trees, and trees to the trees or blobs that they contain.
 </p>
 </dd>
 <dt>
@@ -981,7 +984,7 @@ the git-list &lt;git@vger.kernel.org&gt;.</p>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 01-Jan-2007 03:20:17 UTC
+Last updated 08-Jan-2007 06:53:26 UTC
 </div>
 </div>
 </body>
diff --git a/glossary.txt b/glossary.txt
index 7c1a6592c..cd61aa260 100644
--- 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 a18536c95..5b4102f94 100644
--- a/tutorial-2.html
+++ b/tutorial-2.html
@@ -278,7 +278,7 @@ of the git documentation.</p>
 <div class="content">
 <pre><tt>$ mkdir test-project
 $ cd test-project
-$ git init-db
+$ git init
 Initialized empty Git repository in .git/
 $ echo 'hello world' &gt; file.txt
 $ git add .
@@ -646,7 +646,7 @@ example, creating a new commit.</p>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 16-Dec-2006 07:43:54 UTC
+Last updated 08-Jan-2007 06:53:24 UTC
 </div>
 </div>
 </body>
diff --git a/tutorial-2.txt b/tutorial-2.txt
index 60e54777d..f48894c9a 100644
--- 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 66b00fc72..d88def37e 100644
--- a/tutorial.html
+++ b/tutorial.html
@@ -291,7 +291,7 @@ can place it under git revision control as follows.</p>
 <div class="content">
 <pre><tt>$ tar xzf project.tar.gz
 $ cd project
-$ git init-db</tt></pre>
+$ git init</tt></pre>
 </div></div>
 <p>Git will reply</p>
 <div class="listingblock">
@@ -785,7 +785,7 @@ digressions that may be interesting at this point are:</p>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 07-Jan-2007 07:43:51 UTC
+Last updated 08-Jan-2007 06:53:23 UTC
 </div>
 </div>
 </body>
diff --git a/tutorial.txt b/tutorial.txt
index 01d4a47a9..d2bf0b905 100644
--- 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