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

[PATCH 2/2] Documentation: git-add does not update files marked "assume unchanged"

From
Clemens Buchacher <drizzd@aon.at>
Date
May 1, 2010, 09:27 UTC
Message-ID
<20100501092720.GB15941@localhost>
In-Reply-To
<20100501092512.GA15941@localhost>
Signed-off-by: Clemens Buchacher <drizzd@aon.at>
---

Behavior of git-add also changed since commit 1dcafcc0, but I actually prefer it this way.

 Documentation/git-update-index.txt |    5 ++---
 1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt
index 68dc187..2d45774 100644
--- a/Documentation/git-update-index.txt
+++ b/Documentation/git-update-index.txt
@@ -93,8 +93,6 @@ OPTIONS
 This option can be also used as a coarse file-level mechanism
 to ignore uncommitted changes in tracked files (akin to what
 `.gitignore` does for untracked files).
-You should remember that an explicit 'git add' operation will
-still cause the file to be refreshed from the working tree.
 Git will fail (gracefully) in case it needs to modify this file
 in the index e.g. when merging in a commit;
 thus, in case the assumed-untracked file is changed upstream,
@@ -102,7 +100,8 @@ you will need to handle the situation manually.
 
 --really-refresh::
 	Like '--refresh', but checks stat information unconditionally,
-	without regard to the "assume unchanged" setting.
+	without regard to the "assume unchanged" setting. The "assume
+	unchanged" bit is unset for all paths.
 
 --skip-worktree::
 --no-skip-worktree::
-- 
1.7.0.5.3.ga76e
Previous: Clemens BuchacherNext: Clemens Buchacher
Message 2 of 7 in “do not overwrite files marked "assume unchanged"”
  1. 1/2 do not overwrite files marked "assume unchanged"Clemens Buchacher, May 1, 2010
  2. 2/2 Documentation: git-add does not update files marked "assume unchanged"Clemens Buchacher, May 1, 2010
  3. update-index --really-refresh unsets assume-unchanged bitClemens Buchacher, May 4, 2010
  4. Avery PennarunMay 4, 2010
  5. Clemens BuchacherMay 4, 2010
  6. Junio C HamanoMay 4, 2010
  7. Clemens BuchacherMay 5, 2010

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.