Hey Duy,
I'm not sure why the pattern would have to be as you describe - I'm
just looking to ignore `*.out` as a general configuration, and disable
it for one specific project, so it would seem a plain `!*.out` should
work.
In any case, I added a `.gitignore` file with the single pattern
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
On Sun, Oct 12, 2014 at 9:58 AM, 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
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
4 matches
Mail list logo
