git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] doc: core.ignoreStat clarify the --assume-unchanged effect

From
Philip Oakley <philipoakley@iee.org>
Date
Dec 11, 2014, 23:48 UTC
Message-ID
<1418341733-1656-2-git-send-email-philipoakley@iee.org>
In-Reply-To
<1418341733-1656-1-git-send-email-philipoakley@iee.org>

The assume-unchanged bit can be misunderstood. Be assertive about the expectation that file changes should update that flag.

Signed-off-by: Philip Oakley <philipoakley@iee.org>
---
 Documentation/config.txt | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index c26a7c8..81570b7 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -354,10 +354,11 @@ proxy use, while defaulting to a common proxy for external domains.
 core.ignoreStat::
 	If true, commands which modify both the working tree and the index
 	will mark the updated paths with the "assume unchanged" bit in the
-	index. These marked files are then assumed to stay unchanged in the
-	working tree, until you mark them otherwise manually - Git will not
-	detect the file changes	by lstat() calls. This is useful on systems
-	where those are very slow, such as Microsoft Windows.
+	index. These marked files are then expected to stay unchanged in the
+	working tree. If you change them you should mark their update manually.
+	Git will normally not detect the file changes by lstat() calls.
+	This is useful on systems where those calls are very slow, such as
+	cifs/Microsoft Windows.
 	See linkgit:git-update-index[1].
 	False by default.
 
-- 
1.9.4.msysgit.0
Previous: Philip OakleyNext: Johannes Schindelin
Message 2 of 4 in “core.ignoreStat is affected by --assume-unchanged misunderstandings”
  1. core.ignoreStat is affected by --assume-unchanged misunderstandingsPhilip Oakley, Dec 11, 2014
  2. doc: core.ignoreStat clarify the --assume-unchanged effectPhilip Oakley, Dec 11, 2014
  3. Johannes SchindelinDec 12, 2014
  4. Philip OakleyDec 13, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.