the working copy are ignored; useful on broken filesystems like FAT.
See linkgit:git-update-index[1]. True by default.
+core.trustctime::
+ If false, the ctime differences between the index and the
+ working copy are ignored; useful when the inode change time
+ is regularly modified by something outside Git (file system
+ crawlers and some backup systems).
+ See linkgit:git-update-index[1]. True by default.
+
core.quotepath::
The commands that output paths (e.g. 'ls-files',
'diff'), when not given the `-z` option, will quote
</p>\r
</dd>\r
<dt>\r
+core.trustctime\r
+</dt>\r
+<dd>\r
+<p>\r
+ If false, the ctime differences between the index and the\r
+ working copy are ignored; useful when the inode change time\r
+ is regularly modified by something outside Git (file system\r
+ crawlers and some backup systems).\r
+ See <a href="git-update-index.html">git-update-index(1)</a>. True by default.\r
+</p>\r
+</dd>\r
+<dt>\r
core.quotepath\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 2008-07-28 00:02:59 UTC\r
+Last updated 2008-07-29 08:16:52 UTC\r
</div>\r
</div>\r
</body>\r
</dt>\r
<dd>\r
<p>\r
- Show stage files in the output\r
+ Show staged contents' object name, mode bits and stage number in the output.\r
</p>\r
</dd>\r
<dt>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 2008-07-06 05:16:52 UTC\r
+Last updated 2008-07-29 08:16:52 UTC\r
</div>\r
</div>\r
</body>\r
-s::
--stage::
- Show stage files in the output
+ Show staged contents' object name, mode bits and stage number in the output.
--directory::
If a whole directory is classified as "other", show just its
<h2 id="_description">DESCRIPTION</h2>\r
<div class="sectionbody">\r
<div class="para"><p>Lists the contents of a given tree object, like what "/bin/ls -a" does\r
-in the current working directory. Note that the usage is subtly different,\r
-though - <em>paths</em> denote just a list of patterns to match, e.g. so specifying\r
-directory name (without <em>-r</em>) will behave differently, and order of the\r
-arguments does not matter.</p></div>\r
+in the current working directory. Note that:</p></div>\r
+<div class="ilist"><ul>\r
+<li>\r
+<p>\r
+the behaviour is slightly different from that of "/bin/ls" in that the\r
+ <em>paths</em> denote just a list of patterns to match, e.g. so specifying\r
+ directory name (without <em>-r</em>) will behave differently, and order of the\r
+ arguments does not matter.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+the behaviour is similar to that of "/bin/ls" in that the <em>paths</em> is\r
+ taken as relative to the current working directory. E.g. when you are\r
+ in a directory <em>sub</em> that has a directory <em>dir</em>, you can run <em>git\r
+ ls-tree -r HEAD dir</em> to list the contents of the tree (that is\r
+ <em>sub/dir</em> in <em>HEAD</em>). You don't want to give a tree that is not at the\r
+ root level (e.g. <em>git ls-tree -r HEAD:sub dir</em>) in this case, as that\r
+ would result in asking for <em>sub/sub/dir</em> in the <em>HEAD</em> commit.\r
+</p>\r
+</li>\r
+</ul></div>\r
</div>\r
<h2 id="_options">OPTIONS</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 2008-07-22 09:19:11 UTC\r
+Last updated 2008-07-29 08:16:53 UTC\r
</div>\r
</div>\r
</body>\r
DESCRIPTION
-----------
Lists the contents of a given tree object, like what "/bin/ls -a" does
-in the current working directory. Note that the usage is subtly different,
-though - 'paths' denote just a list of patterns to match, e.g. so specifying
-directory name (without '-r') will behave differently, and order of the
-arguments does not matter.
+in the current working directory. Note that:
+
+ - the behaviour is slightly different from that of "/bin/ls" in that the
+ 'paths' denote just a list of patterns to match, e.g. so specifying
+ directory name (without '-r') will behave differently, and order of the
+ arguments does not matter.
+
+ - the behaviour is similar to that of "/bin/ls" in that the 'paths' is
+ taken as relative to the current working directory. E.g. when you are
+ in a directory 'sub' that has a directory 'dir', you can run 'git
+ ls-tree -r HEAD dir' to list the contents of the tree (that is
+ 'sub/dir' in 'HEAD'). You don't want to give a tree that is not at the
+ root level (e.g. 'git ls-tree -r HEAD:sub dir') in this case, as that
+ would result in asking for 'sub/sub/dir' in the 'HEAD' commit.
OPTIONS
-------
from symbolic link to regular file.</p></div>\r
<div class="para"><p>The command looks at <tt>core.ignorestat</tt> configuration variable. See\r
<em>Using "assume unchanged" bit</em> section above.</p></div>\r
+<div class="para"><p>The command also looks at <tt>core.trustctime</tt> configuration variable.\r
+It can be useful when the inode change time is regularly modified by\r
+something outside Git (file system crawlers and backup systems use\r
+ctime for marking files processed) (see <a href="git-config.html">git-config(1)</a>).</p></div>\r
</div>\r
<h2 id="_see_also">SEE ALSO</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 2008-07-20 01:23:35 UTC\r
+Last updated 2008-07-29 08:16:53 UTC\r
</div>\r
</div>\r
</body>\r
The command looks at `core.ignorestat` configuration variable. See
'Using "assume unchanged" bit' section above.
+The command also looks at `core.trustctime` configuration variable.
+It can be useful when the inode change time is regularly modified by
+something outside Git (file system crawlers and backup systems use
+ctime for marking files processed) (see linkgit:git-config[1]).
+
SEE ALSO
--------