From: Philip Oakley <philipoakley@iee.org>
To: GitList <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Cc: ?utf-8?Q?S=C3=A9rgio?= Basto <sergio@serjux.com>,
Duy Nguyen <pclouds@gmail.com>, Johannes Sixt <j6t@kdbg.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: [PATCH] doc: core.ignoreStat clarify the --assume-unchanged effect
Date: Thu, 11 Dec 2014 23:48:53 +0000 [thread overview]
Message-ID: <1418341733-1656-2-git-send-email-philipoakley@iee.org> (raw)
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
next prev parent reply other threads:[~2014-12-11 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 23:48 [PATCH] core.ignoreStat is affected by --assume-unchanged misunderstandings Philip Oakley
2014-12-11 23:48 ` Philip Oakley [this message]
2014-12-12 10:56 ` [PATCH] doc: core.ignoreStat clarify the --assume-unchanged effect Johannes Schindelin
2014-12-13 20:39 ` Philip Oakley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1418341733-1656-2-git-send-email-philipoakley@iee.org \
--to=philipoakley@iee.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=pclouds@gmail.com \
--cc=sergio@serjux.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).