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

Re: info/exclude not working

From
Jeff King <peff@peff.net>
Date
Jun 3, 2013, 20:32 UTC
Message-ID
<20130603203226.GA23224@sigill.intra.peff.net>
In-Reply-To
<CALy29pLQ-LWg0knzbzLoQfwSt+df_b3tNdWk7OeSN-CjkJhfsQ@mail.gmail.com>
On Mon, Jun 03, 2013 at 01:04:39PM -0700, Devin Rhode wrote:
Show 17 quoted lines
> MBP:dish devin$ cat ../.git/info/exclude
> # git ls-files --others --exclude-from=.git/info/exclude
> # Lines that start with '#' are comments.
> # For a project mostly in C, the following would be a good set of
> # exclude patterns (uncomment them if you want to use them):
> # *.[oa]
> # *~
> models/CAFE.json
> dish/models/CAFE.json
> 
> MBP:dish devin$ git status
> # On branch master
> # Changes not staged for commit:
> #   (use "git add <file>..." to update what will be committed)
> #   (use "git checkout -- <file>..." to discard changes in working directory)
> #
> # modified:   models/CAFE.json ***Shouldn't appear

The exclude mechanism does not mean "do not ever look at this file". It means "when you are adding untracked files, do not include this one". Somebody has already added the file to the repository before your exclude was in place, so it is a tracked file.

There is currently no official mechanism in git to do what you want (there are some hacks, but they include many pitfalls).

-Peff
Previous: Devin RhodeNext: Devin Rhode
Message 2 of 3 in “info/exclude not working”
  1. Devin RhodeJun 3, 2013
  2. Jeff KingJun 3, 2013
  3. Devin RhodeJun 3, 2013

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.