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

Re: getting git to ignore modifications to specific files

From
Jan Krüger <jk@jk.gs>
Date
Sep 2, 2010, 09:25 UTC
Message-ID
<20100902112531.160b09bd@jk.gs>
In-Reply-To
<4C7EA1FF.8030307@gmail.com>
Chris Packham <judge.packham@gmail.com> wrote:
> I did a bit of googling and found
>   git update-index --assume-unchanged
> 
> Which works locally to stop git status from complaining.

Be careful with that, as it's technically meant to be used for another purpose (e.g. slow filesystems). Notably, git reset --hard will still kill your local modifications. In your case it seems to be about automatically generated files so it's no big problem, but it might still cause a bit of confusion, so I thought I'd warn you anyway.

-Jan
Previous: Jonathan NiederNext: Michael J Gruber
Message 7 of 9 in “getting git to ignore modifications to specific files”
  1. Chris PackhamSep 1, 2010
  2. Joshua JensenSep 1, 2010
  3. Bruce KorbSep 1, 2010
  4. Chris PackhamSep 1, 2010
  5. Joshua JuranSep 1, 2010
  6. Jonathan NiederSep 2, 2010
  7. Jan KrügerSep 2, 2010
  8. Michael J GruberSep 2, 2010
  9. Chris PackhamSep 2, 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.