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

Git 2.7.0 gitignore behaviour regression

From
MMMike McQuaid <mike@mikemcquaid.com>
Date
Jan 5, 2016, 14:40 UTC
Message-ID
<4B0F686D-3DF9-4E5D-971D-DB106C6573FD@mikemcquaid.com>
Hi folks,
Firstly, thanks for all your hard work on Git. It makes my life much easier.
Homebrew has a series of convoluted .gitignore rules due to our special/weird use-case of wanting to ignore everything in a working directory except a select few files/directories. We experienced a bug with our .gitignore file for users using Git 2.7.0. This may well be a valid WONTFIX or intentional behaviour change but I wanted to flag it in case it wasn’t.
Here’s a minimal test case:
- Create an empty git repository in a directory with `git init`
- Create a directory named ‘a' containing a file named ‘b' with `mkdir a && touch a/b`
- Create a ‘gitignore’ file with the following contents:
```
*/
/a
!/a/*
```
- Run `git status --short`.

The output with Git 2.6.4 is: ``` ?? .gitignore ```

The output with Git 2.7.0 is: ``` ?? .gitignore ?? a/ ```

Another minimal test case:
- Create an empty git repository in a directory with `git init`
- Create a directory named ‘a' containing a file named ‘b' with `mkdir a && touch a/b`
- Create a ‘gitignore’ file with the following contents:
```
*/
/a
!/a/
```
- Run `git status —short`.

The output with Git 2.6.4 is: ``` ?? .gitignore ?? a/ ```

The output with Git 2.7.0 is: ``` ?? .gitignore ```

Let me know if you need any more information, thanks!

Mike McQuaid http://mikemcquaid.com

Next: Jeff King
Message 1 of 13 in “Git 2.7.0 gitignore behaviour regression”
  1. Mike McQuaidJan 5, 2016
  2. Jeff KingJan 5, 2016
  3. Duy NguyenJan 6, 2016
  4. Mike McQuaidJan 6, 2016
  5. Duy NguyenJan 6, 2016
  6. Junio C HamanoJan 6, 2016
  7. Jeff KingJan 7, 2016
  8. Duy NguyenJan 7, 2016
  9. Carlos Martín NietoJan 8, 2016
  10. brian m. carlsonJan 7, 2016
  11. Duy NguyenJan 8, 2016
  12. brian m. carlsonJan 8, 2016
  13. Duy NguyenJan 8, 2016

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.