{"thread":{"id":"34047","subject":"feature suggestion","startedAt":"2013-06-07T08:59:48Z","lastAt":"2013-06-07T08:59:48Z","messageCount":1,"participants":["Daniel Krikun"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"219615","messageId":"CAMohcw0exP7pDnas4zceoKEADs58axEHYUd6y_MtSoV5=6rMDA@mail.gmail.com","threadId":"34047","inReplyTo":null,"subject":"feature suggestion","fromName":"Daniel Krikun","fromEmail":"krikun.daniel@gmail.com","sentAt":"2013-06-07T08:59:48Z","receivedAt":"2013-06-07T08:59:48Z","isPatch":false,"sender":{"key":"krikun.daniel@gmail.com","avatar":null},"body":"Hi all,\n\nProblem (scenario):\n\n1. A file `file.xyz` has been added and commited\n2. Some time after, let's say `*.xyz` is added to `.gitignore`\n(probably by another contributor)\n    Nobody notices that `file.xyz` is already tracked by git because\nthe file is not modified.\n3. Another person accidentally changes `file.xyz` (may be it some\nlocal config etc.), but no problem it is ignored anyway,... wait, why\ndoes it shows up in `git status` as modified? Maybe it is not in\n.gitignore? ... no it is... you get the point.\n\n\nThe suggestion is that when the .gitignore is updated, some kind of\n`git ls-files --others -i --exclude-standard` is rerun and if there\nare tracked files that are ignored due to the last update to\n.gitignore an appropriate warning is shown.\nThis will eliminate the described surprise factor.\n\nSincerely,\n\n--\nDaniel Krikun\n"}]}