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

Re: Ignoring local changes

From
PPazu <pazu@pazu.com.br>
Date
Dec 14, 2006, 16:55 UTC
Message-ID
<9e7ab7380612140855p1f4ee6c1l5ef24c4d1d169da6@mail.gmail.com>
In-Reply-To
<45817F8A.3050701@op5.se>
2006/12/14, Andreas Ericsson <ae@op5.se>:
> Correction: I just tested this, and while git-add won't touch the file,
> git-update-index will, and git-status still shows it as modified.

Yes, and that's exactly my problems. There are a number of modified/removed files in my working copy that were previously added to the repository, and git-status shows them as modified/removed, even when they're listed in .gitignore or .git/info/exclude

> This feels like a bug to me.

Dunno, sounds like this is by design. I acknowledge that my situation is unusual, and most often, you'll want to always track a file once it's been added to the repository.

Previous: Andreas EricssonNext: Rogan Dawes
Message 3 of 7 in “Ignoring local changes”
  1. PazuDec 14, 2006
  2. Andreas EricssonDec 14, 2006
  3. PazuDec 14, 2006
  4. Rogan DawesDec 14, 2006
  5. PazuDec 14, 2006
  6. PazuDec 14, 2006
  7. Johannes SchindelinDec 15, 2006

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.