From 90ccff355e6fc4705005296023480aa3c957ce7e Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Tue, 29 Jul 2008 08:17:24 +0000 Subject: [PATCH] Autogenerated HTML docs for v1.6.0-rc1-11-g1ce47 --- config.txt | 7 +++++++ git-config.html | 14 +++++++++++++- git-ls-files.html | 4 ++-- git-ls-files.txt | 2 +- git-ls-tree.html | 28 +++++++++++++++++++++++----- git-ls-tree.txt | 18 ++++++++++++++---- git-update-index.html | 6 +++++- git-update-index.txt | 5 +++++ 8 files changed, 70 insertions(+), 14 deletions(-) diff --git a/config.txt b/config.txt index 1a13abc92..61c376057 100644 --- a/config.txt +++ b/config.txt @@ -117,6 +117,13 @@ core.fileMode:: 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 diff --git a/git-config.html b/git-config.html index ce34a345d..b85ee88ce 100644 --- a/git-config.html +++ b/git-config.html @@ -863,6 +863,18 @@ core.fileMode

+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 git-update-index(1). True by default. +

+
+
core.quotepath
@@ -2688,7 +2700,7 @@ web.browser diff --git a/git-ls-files.html b/git-ls-files.html index 934a06db6..47ee69237 100644 --- a/git-ls-files.html +++ b/git-ls-files.html @@ -406,7 +406,7 @@ shown:

- Show stage files in the output + Show staged contents' object name, mode bits and stage number in the output.

@@ -704,7 +704,7 @@ pattern file appears in.

diff --git a/git-ls-files.txt b/git-ls-files.txt index f43af4174..9f85d60b5 100644 --- a/git-ls-files.txt +++ b/git-ls-files.txt @@ -53,7 +53,7 @@ OPTIONS -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 diff --git a/git-ls-tree.html b/git-ls-tree.html index 435b8bbc6..39a8558a6 100644 --- a/git-ls-tree.html +++ b/git-ls-tree.html @@ -328,10 +328,28 @@ git-ls-tree(1) Manual Page

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

@@ -464,7 +482,7 @@ another major rewrite by Linus Torvalds <torvalds@osdl.org>

diff --git a/git-ls-tree.txt b/git-ls-tree.txt index d7e73f568..4c7262f1c 100644 --- a/git-ls-tree.txt +++ b/git-ls-tree.txt @@ -16,10 +16,20 @@ SYNOPSIS 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 ------- diff --git a/git-update-index.html b/git-update-index.html index 90099e2cd..146b87956 100644 --- a/git-update-index.html +++ b/git-update-index.html @@ -770,6 +770,10 @@ as plain files, and this command does not modify a recorded file mode from symbolic link to regular file.

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 git-config(1)).

SEE ALSO

@@ -790,7 +794,7 @@ from symbolic link to regular file.

diff --git a/git-update-index.txt b/git-update-index.txt index 6b930bc16..1d9d81a70 100644 --- a/git-update-index.txt +++ b/git-update-index.txt @@ -323,6 +323,11 @@ from symbolic link to regular file. 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 -------- -- 2.26.2