I used `check-ignore -v`, and the `.out` file is being ignored by the `*.out` pattern in the `core.excludesfile` file. Its parent folder is not being ignored. So as a rule, `core.excludesfile` overrides `$GIT_DIR/info/exclude`.
That doesn't make much sense to me, because I'm much more likely to want to override global exclusions for a specific project, than override specific project settings with a global exclusion file (that last one really makes no sense imho). Thoughts? On Sat, Oct 11, 2014 at 10:58 PM, Dun Peal <dunpea...@gmail.com> wrote: > I have the pattern `*.out` defined in my `core.excludesfile`. > According to the documentation[1], patterns defined in > `$GIT_DIR/info/exclude` take precedence over `core.excludesfile`, so > for one particular project that needs to track some `.out` files, I > created `$GIT_DIR/info/exclude` with just one pattern: `!*.out`. > > Yet for some reason, `git status` still fails to report newly created > `.out` files for that project. Am I misunderstanding the > documentation? > > Thanks, D. > > [1] http://jk.gs/gitignore.html -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
