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

[PATCH] gitignore.txt: do not suggest assume-unchanged

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Dec 9, 2014, 11:13 UTC
Message-ID
<fe381f27dd50afd44d451577e2315ed5580e3034.1418123458.git.git@drmicha.warpmail.net>
In-Reply-To
<5486B342.8090800@drmicha.warpmail.net>

git-update-index --assume-unchanged was never meant to ignore changes to tracked files (only to spare some stats). So do not suggest it as a means to achieve that.

Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
---
 Documentation/gitignore.txt | 4 ----
 1 file changed, 4 deletions(-)
diff --git a/Documentation/gitignore.txt b/Documentation/gitignore.txt
index 09e82c3..4fd0442 100644
--- a/Documentation/gitignore.txt
+++ b/Documentation/gitignore.txt
@@ -138,9 +138,6 @@ NOTES
 The purpose of gitignore files is to ensure that certain files
 not tracked by Git remain untracked.
 
-To ignore uncommitted changes in a file that is already tracked,
-use 'git update-index {litdd}assume-unchanged'.
-
 To stop tracking a file that is currently tracked, use
 'git rm --cached'.
 
@@ -203,7 +200,6 @@ everything within `foo/bar`):
 SEE ALSO
 --------
 linkgit:git-rm[1],
-linkgit:git-update-index[1],
 linkgit:gitrepository-layout[5],
 linkgit:git-check-ignore[1]
 
-- 
2.2.0.345.g7041aac
Previous: Michael J GruberNext: Jonathan Nieder
Message 7 of 11 in “Improve --assume-unchanged in the git update-index man page”
  1. Improve --assume-unchanged in the git update-index man pagePhilip Oakley, Dec 6, 2014
  2. doc: make clear --assume-unchanged's user contractPhilip Oakley, Dec 6, 2014
  3. Sérgio BastoDec 9, 2014
  4. Philip OakleyDec 9, 2014
  5. Philip OakleyDec 9, 2014
  6. Michael J GruberDec 9, 2014
  7. gitignore.txt: do not suggest assume-unchangedMichael J Gruber, Dec 9, 2014
  8. Jonathan NiederDec 10, 2014
  9. Michael J GruberDec 11, 2014
  10. Junio C HamanoDec 10, 2014
  11. Sérgio BastoDec 10, 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.