From: Dun Peal <dunpealer@gmail.com>
Date: Sun, 12 Oct 2014 14:48:06 GMT
Subject: Re: $GIT_DIR/info/exclude fails to negate a pattern defined by core.excludesfile
Message-ID: <CAD03jn5_LY4gr68bCO1axXiGxCwX9xZeywD9uGoZdsXqzynBWQ@mail.gmail.com>
In-Reply-To: <CAD03jn4md9YJZ3fFWmvjiO2KSztc-02QpznXO3LJeiZDz8YhrQ@mail.gmail.com>

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 <dunpealer@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