From: Junio C Hamano <junio@hera.kernel.org>
Date: Wed, 22 Feb 2006 10:44:55 +0000 (+0000)
Subject: Autogenerated HTML docs for v1.2.2-g50319
X-Git-Url: https://git.octo.it/?a=commitdiff_plain;h=7e9f6b7094a99335837f79e33c7723ff516dc53b;p=git.git

Autogenerated HTML docs for v1.2.2-g50319
---

diff --git a/git-add.html b/git-add.html
index f47ba086..bc76ff8a 100644
--- a/git-add.html
+++ b/git-add.html
@@ -3,7 +3,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 7.0.1" />
+<meta name="generator" content="AsciiDoc 7.0.2" />
 <style type="text/css">
 /* Debug borders */
 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
@@ -272,7 +272,7 @@ git-add(1) Manual Page
 </div>
 <h2>SYNOPSIS</h2>
 <div class="sectionbody">
-<p><em>git-add</em> [-n] [-v] &lt;file&gt;&#8230;</p>
+<p><em>git-add</em> [-n] [-v] [--] &lt;file&gt;&#8230;</p>
 </div>
 <h2>DESCRIPTION</h2>
 <div class="sectionbody">
@@ -306,6 +306,16 @@ for people used to do "cvs add".</p>
         Be verbose.
 </p>
 </dd>
+<dt>
+&#8212;
+</dt>
+<dd>
+<p>
+        This option can be used to separate command-line options from
+        the list of files, (useful when filenames might be mistaken
+        for command-line options).
+</p>
+</dd>
 </dl>
 </div>
 <h2>DISCUSSION</h2>
@@ -371,7 +381,7 @@ git-add git-*.sh
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 06-Jan-2006 17:11:58 PDT
+Last updated 22-Feb-2006 10:44:46 UTC
 </div>
 </div>
 </body>
diff --git a/git-add.txt b/git-add.txt
index 89e46140..7e293834 100644
--- a/git-add.txt
+++ b/git-add.txt
@@ -7,7 +7,7 @@ git-add - Add files to the index file.
 
 SYNOPSIS
 --------
-'git-add' [-n] [-v] <file>...
+'git-add' [-n] [-v] [--] <file>...
 
 DESCRIPTION
 -----------
@@ -26,6 +26,11 @@ OPTIONS
 -v::
         Be verbose.
 
+--::
+	This option can be used to separate command-line options from
+	the list of files, (useful when filenames might be mistaken
+	for command-line options).
+
 
 DISCUSSION
 ----------
diff --git a/git-ls-files.html b/git-ls-files.html
index 129ef2b0..ed81380b 100644
--- a/git-ls-files.html
+++ b/git-ls-files.html
@@ -272,13 +272,15 @@ git-ls-files(1) Manual Page
 </div>
 <h2>SYNOPSIS</h2>
 <div class="sectionbody">
-<p><em>git-ls-files</em> [-z] [-t]
+<div class="verseblock">
+<div class="content"><em>git-ls-files</em> [-z] [-t] [-v]
                 (--[cached|deleted|others|ignored|stage|unmerged|killed|modified])*
                 (-[c|d|o|i|s|u|k|m])*
                 [-x &lt;pattern&gt;|--exclude=&lt;pattern&gt;]
                 [-X &lt;file&gt;|--exclude-from=&lt;file&gt;]
                 [--exclude-per-directory=&lt;file&gt;]
-                [--full-name] [--] [&lt;file&gt;]*</p>
+                [--error-unmatch]
+                [--full-name] [--] [&lt;file&gt;]*</div></div>
 </div>
 <h2>DESCRIPTION</h2>
 <div class="sectionbody">
@@ -402,6 +404,15 @@ shown:</p>
 </p>
 </dd>
 <dt>
+--error-unmatch
+</dt>
+<dd>
+<p>
+        If any &lt;file&gt; does not appear in the index, treat this as an
+        error (return 1).
+</p>
+</dd>
+<dt>
 -t
 </dt>
 <dd>
@@ -461,6 +472,15 @@ other
 </table></div>
 </dd>
 <dt>
+-v
+</dt>
+<dd>
+<p>
+        Similar to <tt>-t</tt>, but use lowercase letters for files
+        that are marked as <em>always matching index</em>.
+</p>
+</dd>
+<dt>
 --full-name
 </dt>
 <dd>
@@ -640,7 +660,7 @@ otherwise, it is a shell glob pattern, suitable for
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 14-Feb-2006 07:59:59 UTC
+Last updated 22-Feb-2006 10:44:46 UTC
 </div>
 </div>
 </body>
diff --git a/git-ls-files.txt b/git-ls-files.txt
index fe534129..e813f842 100644
--- a/git-ls-files.txt
+++ b/git-ls-files.txt
@@ -8,12 +8,14 @@ git-ls-files - Information about files in the index/working directory
 
 SYNOPSIS
 --------
-'git-ls-files' [-z] [-t]
+[verse]
+'git-ls-files' [-z] [-t] [-v]
 		(--[cached|deleted|others|ignored|stage|unmerged|killed|modified])\*
 		(-[c|d|o|i|s|u|k|m])\*
 		[-x <pattern>|--exclude=<pattern>]
 		[-X <file>|--exclude-from=<file>]
 		[--exclude-per-directory=<file>] 
+		[--error-unmatch]
 		[--full-name] [--] [<file>]\*
 
 DESCRIPTION
@@ -72,6 +74,10 @@ OPTIONS
 	read additional exclude patterns that apply only to the
 	directory and its subdirectories in <file>.
 
+--error-unmatch::
+	If any <file> does not appear in the index, treat this as an
+	error (return 1).
+
 -t::
 	Identify the file status with the following tags (followed by
 	a space) at the start of each line:
@@ -82,6 +88,10 @@ OPTIONS
 	K::	to be killed
 	?::	other
 
+-v::
+	Similar to `-t`, but use lowercase letters for files
+	that are marked as 'always matching index'.
+
 --full-name::
 	When run from a subdirectory, the command usually
 	outputs paths relative to the current directory.  This
diff --git a/git-pack-objects.html b/git-pack-objects.html
index e5635bcd..b54eb917 100644
--- a/git-pack-objects.html
+++ b/git-pack-objects.html
@@ -3,7 +3,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 7.0.1" />
+<meta name="generator" content="AsciiDoc 7.0.2" />
 <style type="text/css">
 /* Debug borders */
 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
@@ -272,7 +272,10 @@ git-pack-objects(1) Manual Page
 </div>
 <h2>SYNOPSIS</h2>
 <div class="sectionbody">
-<p><em>git-pack-objects</em> [--non-empty] [--local] [--incremental] [--window=N] [--depth=N] {--stdout | base-name} &lt; object-list</p>
+<div class="verseblock">
+<div class="content"><em>git-pack-objects</em> [-q] [--no-reuse-delta] [--non-empty]
+        [--local] [--incremental] [--window=N] [--depth=N]
+        {--stdout | base-name} &lt; object-list</div></div>
 </div>
 <h2>DESCRIPTION</h2>
 <div class="sectionbody">
@@ -291,6 +294,9 @@ transport by their peers.</p>
 <p>Placing both in the pack/ subdirectory of $GIT_OBJECT_DIRECTORY (or
 any of the directories on $GIT_ALTERNATE_OBJECT_DIRECTORIES)
 enables git to read from such an archive.</p>
+<p>In a packed archive, an object is either stored as a compressed
+whole, or as a difference from some other object.  The latter is
+often called a delta.</p>
 </div>
 <h2>OPTIONS</h2>
 <div class="sectionbody">
@@ -364,6 +370,27 @@ base-name
         least one object.
 </p>
 </dd>
+<dt>
+-q
+</dt>
+<dd>
+<p>
+        This flag makes the command not to report its progress
+        on the standard error stream.
+</p>
+</dd>
+<dt>
+--no-reuse-delta
+</dt>
+<dd>
+<p>
+        When creating a packed archive in a repository that
+        has existing packs, the command reuses existing deltas.
+        This sometimes results in a slightly suboptimal pack.
+        This flag tells the command not to reuse existing deltas
+        but compute them from scratch.
+</p>
+</dd>
 </dl>
 </div>
 <h2>Author</h2>
@@ -385,7 +412,7 @@ base-name
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 06-Jan-2006 17:12:41 PDT
+Last updated 22-Feb-2006 10:44:47 UTC
 </div>
 </div>
 </body>
diff --git a/git-pack-objects.txt b/git-pack-objects.txt
index 2d67d391..4cb2e83f 100644
--- a/git-pack-objects.txt
+++ b/git-pack-objects.txt
@@ -8,7 +8,10 @@ git-pack-objects - Create a packed archive of objects.
 
 SYNOPSIS
 --------
-'git-pack-objects' [--non-empty] [--local] [--incremental] [--window=N] [--depth=N] {--stdout | base-name} < object-list
+[verse]
+'git-pack-objects' [-q] [--no-reuse-delta] [--non-empty]
+	[--local] [--incremental] [--window=N] [--depth=N]
+	{--stdout | base-name} < object-list
 
 
 DESCRIPTION
@@ -32,6 +35,10 @@ Placing both in the pack/ subdirectory of $GIT_OBJECT_DIRECTORY (or
 any of the directories on $GIT_ALTERNATE_OBJECT_DIRECTORIES)
 enables git to read from such an archive.
 
+In a packed archive, an object is either stored as a compressed
+whole, or as a difference from some other object.  The latter is
+often called a delta.
+
 
 OPTIONS
 -------
@@ -74,6 +81,18 @@ base-name::
         Only create a packed archive if it would contain at
         least one object.
 
+-q::
+	This flag makes the command not to report its progress
+	on the standard error stream.
+
+--no-reuse-delta::
+	When creating a packed archive in a repository that
+	has existing packs, the command reuses existing deltas.
+	This sometimes results in a slightly suboptimal pack.
+	This flag tells the command not to reuse existing deltas
+	but compute them from scratch.
+
+
 Author
 ------
 Written by Linus Torvalds <torvalds@osdl.org>
diff --git a/git-push.html b/git-push.html
index 5bf5b062..69ec9771 100644
--- a/git-push.html
+++ b/git-push.html
@@ -312,6 +312,11 @@ four parents before the current master head).</p>
 to fast forward the remote ref that matches &lt;dst&gt;.  If
 the optional plus <tt>+</tt> is used, the remote ref is updated
 even if it does not result in a fast forward update.</p>
+<p>Note: If no explicit refspec is found, (that is neither
+on the command line nor in any Push line of the
+corresponding remotes file---see below), then all the
+refs that exist both on the local side and on the remote
+side are updated.</p>
 <p>Some short-cut notations are also supported.</p>
 <ul>
 <li>
@@ -496,7 +501,7 @@ Pull: refs/heads/&lt;head&gt;:&lt;remote&gt;</tt></pre>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 07-Feb-2006 08:04:31 UTC
+Last updated 22-Feb-2006 10:44:47 UTC
 </div>
 </div>
 </body>
diff --git a/git-push.txt b/git-push.txt
index 5b891105..6f4a48a1 100644
--- a/git-push.txt
+++ b/git-push.txt
@@ -43,6 +43,12 @@ to fast forward the remote ref that matches <dst>.  If
 the optional plus `+` is used, the remote ref is updated
 even if it does not result in a fast forward update.
 +
+Note: If no explicit refspec is found, (that is neither
+on the command line nor in any Push line of the
+corresponding remotes file---see below), then all the
+refs that exist both on the local side and on the remote
+side are updated.
++
 Some short-cut notations are also supported.
 +
 * `tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
diff --git a/git-rebase.html b/git-rebase.html
index bf648733..bf0a3af4 100644
--- a/git-rebase.html
+++ b/git-rebase.html
@@ -3,7 +3,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 7.0.1" />
+<meta name="generator" content="AsciiDoc 7.0.2" />
 <style type="text/css">
 /* Debug borders */
 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
@@ -272,16 +272,65 @@ git-rebase(1) Manual Page
 </div>
 <h2>SYNOPSIS</h2>
 <div class="sectionbody">
-<p><em>git-rebase</em> &lt;upstream&gt; [&lt;head&gt;]</p>
+<p><em>git-rebase</em> [--onto &lt;newbase&gt;] &lt;upstream&gt; [&lt;branch&gt;]</p>
 </div>
 <h2>DESCRIPTION</h2>
 <div class="sectionbody">
-<p>Rebases local commits to the new head of the upstream tree.</p>
+<p>git-rebase applies to &lt;upstream&gt; (or optionally to &lt;newbase&gt;) commits
+from &lt;branch&gt; that do not appear in &lt;upstream&gt;. When &lt;branch&gt; is not
+specified it defaults to the current branch (HEAD).</p>
+<p>When git-rebase is complete, &lt;branch&gt; will be updated to point to the
+newly created line of commit objects, so the previous line will not be
+accessible unless there are other references to it already.</p>
+<p>Assume the following history exists and the current branch is "topic":</p>
+<div class="literalblock">
+<div class="content">
+<pre><tt>      A---B---C topic
+     /
+D---E---F---G master</tt></pre>
+</div></div>
+<p>From this point, the result of the following commands:</p>
+<div class="literalblock">
+<div class="content">
+<pre><tt>git-rebase master
+git-rebase master topic</tt></pre>
+</div></div>
+<p>would be:</p>
+<div class="literalblock">
+<div class="content">
+<pre><tt>              A'--B'--C' topic
+             /
+D---E---F---G master</tt></pre>
+</div></div>
+<p>While, starting from the same point, the result of the following
+commands:</p>
+<div class="literalblock">
+<div class="content">
+<pre><tt>git-rebase --onto master~1 master
+git-rebase --onto master~1 master topic</tt></pre>
+</div></div>
+<p>would be:</p>
+<div class="literalblock">
+<div class="content">
+<pre><tt>          A'--B'--C' topic
+         /
+D---E---F---G master</tt></pre>
+</div></div>
 </div>
 <h2>OPTIONS</h2>
 <div class="sectionbody">
 <dl>
 <dt>
+&lt;newbase&gt;
+</dt>
+<dd>
+<p>
+        Starting point at which to create the new commits. If the
+        --onto option is not specified, the starting point is
+        &lt;upstream&gt;.
+</p>
+</dd>
+<dt>
 &lt;upstream&gt;
 </dt>
 <dd>
@@ -313,7 +362,7 @@ git-rebase(1) Manual Page
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 27-Dec-2005 00:16:32 PDT
+Last updated 22-Feb-2006 10:44:47 UTC
 </div>
 </div>
 </body>
diff --git a/git-rebase.txt b/git-rebase.txt
index 16c158f4..f037d128 100644
--- a/git-rebase.txt
+++ b/git-rebase.txt
@@ -7,14 +7,54 @@ git-rebase - Rebase local commits to new upstream head.
 
 SYNOPSIS
 --------
-'git-rebase' <upstream> [<head>]
+'git-rebase' [--onto <newbase>] <upstream> [<branch>]
 
 DESCRIPTION
 -----------
-Rebases local commits to the new head of the upstream tree.
+git-rebase applies to <upstream> (or optionally to <newbase>) commits
+from <branch> that do not appear in <upstream>. When <branch> is not
+specified it defaults to the current branch (HEAD).
+
+When git-rebase is complete, <branch> will be updated to point to the
+newly created line of commit objects, so the previous line will not be
+accessible unless there are other references to it already.
+
+Assume the following history exists and the current branch is "topic":
+
+          A---B---C topic
+         /
+    D---E---F---G master
+
+From this point, the result of the following commands:
+
+    git-rebase master
+    git-rebase master topic
+
+would be:
+
+                  A'--B'--C' topic
+                 /
+    D---E---F---G master
+
+While, starting from the same point, the result of the following
+commands:
+
+    git-rebase --onto master~1 master
+    git-rebase --onto master~1 master topic
+
+would be:
+
+              A'--B'--C' topic
+             /
+    D---E---F---G master
 
 OPTIONS
 -------
+<newbase>::
+	Starting point at which to create the new commits. If the
+	--onto option is not specified, the starting point is
+	<upstream>.
+
 <upstream>::
 	Upstream branch to compare against.
 
diff --git a/git-repack.html b/git-repack.html
index 4066cb80..1fada778 100644
--- a/git-repack.html
+++ b/git-repack.html
@@ -3,7 +3,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 7.0.1" />
+<meta name="generator" content="AsciiDoc 7.0.2" />
 <style type="text/css">
 /* Debug borders */
 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
@@ -272,7 +272,7 @@ git-repack(1) Manual Page
 </div>
 <h2>SYNOPSIS</h2>
 <div class="sectionbody">
-<p><em>git-repack</em> [-a] [-d] [-l] [-n]</p>
+<p><em>git-repack</em> [-a] [-d] [-f] [-l] [-n] [-q]</p>
 </div>
 <h2>DESCRIPTION</h2>
 <div class="sectionbody">
@@ -319,6 +319,24 @@ engines, disk storage, etc.</p>
 </p>
 </dd>
 <dt>
+-f
+</dt>
+<dd>
+<p>
+        Pass the <tt>--no-reuse-delta</tt> option to <tt>git pack-objects</tt>, see
+        <a href="git-pack-objects.html">git-pack-objects(1)</a>.
+</p>
+</dd>
+<dt>
+-q
+</dt>
+<dd>
+<p>
+        Pass the <tt>-q</tt> option to <tt>git pack-objects</tt>, see
+        <a href="git-pack-objects.html">git-pack-objects(1)</a>.
+</p>
+</dd>
+<dt>
 -n
 </dt>
 <dd>
@@ -348,7 +366,7 @@ engines, disk storage, etc.</p>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 27-Dec-2005 00:16:34 PDT
+Last updated 22-Feb-2006 10:44:48 UTC
 </div>
 </div>
 </body>
diff --git a/git-repack.txt b/git-repack.txt
index 9060fe88..6c0f792d 100644
--- a/git-repack.txt
+++ b/git-repack.txt
@@ -9,7 +9,7 @@ objects into pack files.
 
 SYNOPSIS
 --------
-'git-repack' [-a] [-d] [-l] [-n]
+'git-repack' [-a] [-d] [-f] [-l] [-n] [-q]
 
 DESCRIPTION
 -----------
@@ -43,6 +43,14 @@ OPTIONS
         Pass the `--local` option to `git pack-objects`, see
         gitlink:git-pack-objects[1].
 
+-f::
+        Pass the `--no-reuse-delta` option to `git pack-objects`, see
+        gitlink:git-pack-objects[1].
+
+-q::
+        Pass the `-q` option to `git pack-objects`, see
+        gitlink:git-pack-objects[1].
+
 -n::
         Do not update the server information with
         `git update-server-info`.
diff --git a/git-update-index.html b/git-update-index.html
index d97d30dc..19699893 100644
--- a/git-update-index.html
+++ b/git-update-index.html
@@ -3,7 +3,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 7.0.1" />
+<meta name="generator" content="AsciiDoc 7.0.2" />
 <style type="text/css">
 /* Debug borders */
 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
@@ -272,15 +272,18 @@ git-update-index(1) Manual Page
 </div>
 <h2>SYNOPSIS</h2>
 <div class="sectionbody">
-<p><em>git-update-index</em>
+<div class="verseblock">
+<div class="content"><em>git-update-index</em>
              [--add] [--remove | --force-remove] [--replace]
              [--refresh [-q] [--unmerged] [--ignore-missing]]
              [--cacheinfo &lt;mode&gt; &lt;object&gt; &lt;file&gt;]*
              [--chmod=(+|-)x]
+             [--assume-unchanged | --no-assume-unchanged]
+             [--really-refresh]
              [--info-only] [--index-info]
              [-z] [--stdin]
              [--verbose]
-             [--] [&lt;file&gt;]*</p>
+             [--] [&lt;file&gt;]*</div></div>
 </div>
 <h2>DESCRIPTION</h2>
 <div class="sectionbody">
@@ -375,6 +378,23 @@ using the various options:</p>
 </p>
 </dd>
 <dt>
+--assume-unchanged, --no-assume-unchanged
+</dt>
+<dd>
+<p>
+        When these flags are specified, the object name recorded
+        for the paths are not updated.  Instead, these options
+        sets and unsets the "assume unchanged" bit for the
+        paths.  When the "assume unchanged" bit is on, git stops
+        checking the working tree files for possible
+        modifications, so you need to manually unset the bit to
+        tell git when you change the working tree file. This is
+        sometimes helpful when working with a big project on a
+        filesystem that has very slow lstat(2) system call
+        (e.g. cifs).
+</p>
+</dd>
+<dt>
 --info-only
 </dt>
 <dd>
@@ -541,6 +561,33 @@ for that path.  After the above, we would end up with this:</p>
 100755 8a1218a1024a212bb3db30becd860315f9f3ac52 2       frotz</tt></pre>
 </div></div>
 </div>
+<h2>Using "assume unchanged" bit</h2>
+<div class="sectionbody">
+<p>Many operations in git depend on your filesystem to have an
+efficient <tt>lstat(2)</tt> implementation, so that <tt>st_mtime</tt>
+information for working tree files can be cheaply checked to see
+if the file contents have changed from the version recorded in
+the index file.  Unfortunately, some filesystems have
+inefficient <tt>lstat(2)</tt>.  If your filesystem is one of them, you
+can set "assume unchanged" bit to paths you have not changed to
+cause git not to do this check.  Note that setting this bit on a
+path does not mean git will check the contents of the file to
+see if it has changed &#8212; it makes git to omit any checking and
+assume it has <strong>not</strong> changed.  When you make changes to working
+tree files, you have to explicitly tell git about it by dropping
+"assume unchanged" bit, either before or after you modify them.</p>
+<p>In order to set "assume unchanged" bit, use <tt>--assume-unchanged</tt>
+option.  To unset, use <tt>--no-assume-unchanged</tt>.</p>
+<p>The command looks at <tt>core.ignorestat</tt> configuration variable.  When
+this is true, paths updated with <tt>git-update-index paths&#8230;</tt> and
+paths updated with other git commands that update both index and
+working tree (e.g. <tt>git-apply --index</tt>, <tt>git-checkout-index -u</tt>,
+and <tt>git-read-tree -u</tt>) are automatically marked as "assume
+unchanged".  Note that "assume unchanged" bit is <strong>not</strong> set if
+<tt>git-update-index --refresh</tt> finds the working tree file matches
+the index (use <tt>git-update-index --really-refresh</tt> if you want
+to mark them as "assume unchanged").</p>
+</div>
 <h2>Examples</h2>
 <div class="sectionbody">
 <p>To update and refresh only the files already checked out:</p>
@@ -548,6 +595,34 @@ for that path.  After the above, we would end up with this:</p>
 <div class="content">
 <pre><tt>$ git-checkout-index -n -f -a &amp;&amp; git-update-index --ignore-missing --refresh</tt></pre>
 </div></div>
+<p>On an inefficient filesystem with <tt>core.ignorestat</tt> set:</p>
+<div class="listingblock">
+<div class="content">
+<pre><tt>$ git update-index --really-refresh <b>(1)</b>
+$ git update-index --no-assume-unchanged foo.c <b>(2)</b>
+$ git diff --name-only <b>(3)</b>
+$ edit foo.c
+$ git diff --name-only <b>(4)</b>
+M foo.c
+$ git update-index foo.c <b>(5)</b>
+$ git diff --name-only <b>(6)</b>
+$ edit foo.c
+$ git diff --name-only <b>(7)</b>
+$ git update-index --no-assume-unchanged foo.c <b>(8)</b>
+$ git diff --name-only <b>(9)</b>
+M foo.c
+
+<b>(1)</b> forces lstat(2) to set "assume unchanged" bits for paths
+    that match index.
+<b>(2)</b> mark the path to be edited.
+<b>(3)</b> this does lstat(2) and finds index matches the path.
+<b>(4)</b> this does lstat(2) and finds index does not match the path.
+<b>(5)</b> registering the new version to index sets "assume unchanged" bit.
+<b>(6)</b> and it is assumed unchanged.
+<b>(7)</b> even after you edit it.
+<b>(8)</b> you can tell about the change after the fact.
+<b>(9)</b> now it checks with lstat(2) and finds it has been changed.</tt></pre>
+</div></div>
 </div>
 <h2>Configuration</h2>
 <div class="sectionbody">
@@ -558,6 +633,8 @@ This causes the command to ignore differences in file modes recorded
 in the index and the file mode on the filesystem if they differ only on
 executable bit.   On such an unfortunate filesystem, you may
 need to use <tt>git-update-index --chmod=</tt>.</p>
+<p>The command looks at <tt>core.ignorestat</tt> configuration variable.  See
+<em>Using "assume unchanged" bit</em> section above.</p>
 </div>
 <h2>See Also</h2>
 <div class="sectionbody">
@@ -577,7 +654,7 @@ need to use <tt>git-update-index --chmod=</tt>.</p>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 27-Dec-2005 00:16:52 PDT
+Last updated 22-Feb-2006 10:44:48 UTC
 </div>
 </div>
 </body>
diff --git a/git-update-index.txt b/git-update-index.txt
index c74311da..0a1b0ad5 100644
--- a/git-update-index.txt
+++ b/git-update-index.txt
@@ -8,11 +8,14 @@ git-update-index - Modifies the index or directory cache
 
 SYNOPSIS
 --------
+[verse]
 'git-update-index'
 	     [--add] [--remove | --force-remove] [--replace] 
 	     [--refresh [-q] [--unmerged] [--ignore-missing]]
 	     [--cacheinfo <mode> <object> <file>]\*
 	     [--chmod=(+|-)x]
+	     [--assume-unchanged | --no-assume-unchanged]
+	     [--really-refresh]
 	     [--info-only] [--index-info]
 	     [-z] [--stdin]
 	     [--verbose]
@@ -65,6 +68,18 @@ OPTIONS
 --chmod=(+|-)x::
         Set the execute permissions on the updated files.        
 
+--assume-unchanged, --no-assume-unchanged::
+	When these flags are specified, the object name recorded
+	for the paths are not updated.  Instead, these options
+	sets and unsets the "assume unchanged" bit for the
+	paths.  When the "assume unchanged" bit is on, git stops
+	checking the working tree files for possible
+	modifications, so you need to manually unset the bit to
+	tell git when you change the working tree file. This is
+	sometimes helpful when working with a big project on a
+	filesystem that has very slow lstat(2) system call
+	(e.g. cifs).
+
 --info-only::
 	Do not create objects in the object database for all
 	<file> arguments that follow this flag; just insert
@@ -193,6 +208,37 @@ $ git ls-files -s
 ------------
 
 
+Using "assume unchanged" bit
+----------------------------
+
+Many operations in git depend on your filesystem to have an
+efficient `lstat(2)` implementation, so that `st_mtime`
+information for working tree files can be cheaply checked to see
+if the file contents have changed from the version recorded in
+the index file.  Unfortunately, some filesystems have
+inefficient `lstat(2)`.  If your filesystem is one of them, you
+can set "assume unchanged" bit to paths you have not changed to
+cause git not to do this check.  Note that setting this bit on a
+path does not mean git will check the contents of the file to
+see if it has changed -- it makes git to omit any checking and
+assume it has *not* changed.  When you make changes to working
+tree files, you have to explicitly tell git about it by dropping
+"assume unchanged" bit, either before or after you modify them.
+
+In order to set "assume unchanged" bit, use `--assume-unchanged`
+option.  To unset, use `--no-assume-unchanged`.
+
+The command looks at `core.ignorestat` configuration variable.  When
+this is true, paths updated with `git-update-index paths...` and
+paths updated with other git commands that update both index and
+working tree (e.g. `git-apply --index`, `git-checkout-index -u`,
+and `git-read-tree -u`) are automatically marked as "assume
+unchanged".  Note that "assume unchanged" bit is *not* set if
+`git-update-index --refresh` finds the working tree file matches
+the index (use `git-update-index --really-refresh` if you want
+to mark them as "assume unchanged").
+
+
 Examples
 --------
 To update and refresh only the files already checked out:
@@ -201,6 +247,35 @@ To update and refresh only the files already checked out:
 $ git-checkout-index -n -f -a && git-update-index --ignore-missing --refresh
 ----------------
 
+On an inefficient filesystem with `core.ignorestat` set:
+
+------------
+$ git update-index --really-refresh <1>
+$ git update-index --no-assume-unchanged foo.c <2>
+$ git diff --name-only <3>
+$ edit foo.c
+$ git diff --name-only <4>
+M foo.c
+$ git update-index foo.c <5>
+$ git diff --name-only <6>
+$ edit foo.c
+$ git diff --name-only <7>
+$ git update-index --no-assume-unchanged foo.c <8>
+$ git diff --name-only <9>
+M foo.c
+
+<1> forces lstat(2) to set "assume unchanged" bits for paths
+    that match index.
+<2> mark the path to be edited.
+<3> this does lstat(2) and finds index matches the path.
+<4> this does lstat(2) and finds index does not match the path.
+<5> registering the new version to index sets "assume unchanged" bit.
+<6> and it is assumed unchanged.
+<7> even after you edit it.
+<8> you can tell about the change after the fact.
+<9> now it checks with lstat(2) and finds it has been changed.
+------------
+
 
 Configuration
 -------------
@@ -213,6 +288,9 @@ in the index and the file mode on the filesystem if they differ only on
 executable bit.   On such an unfortunate filesystem, you may
 need to use `git-update-index --chmod=`.
 
+The command looks at `core.ignorestat` configuration variable.  See
+'Using "assume unchanged" bit' section above.
+
 
 See Also
 --------
