You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bpo-37936: Avoid ignoring files that we actually do track.
There were about 15 files that are actually in the repo but that are
covered by the rules in .gitignore.
Git itself takes no notice of what .gitignore says about files that
it's already tracking... but the discrepancy can be confusing to a
human that adds a new file unexpectedly covered by these rules, as
well as to non-Git software that looks at .gitignore but doesn't
implement this wrinkle in its semantics. (E.g., `rg`.)
Several of these are from rules that apply more broadly than
intended: for example, `Makefile` applies to `Doc/Makefile` and
`Tools/freeze/test/Makefile`, whereas `/Makefile` means only the
`Makefile` at the repo's root.
The `Modules/Setup` rule simply wasn't updated after 961d54c.
Finally, the `.gitignore` rule simply shouldn't be there at all.
It didn't actually work as intended -- indeed the fact it showed up,
in c5ae169, is exactly the thing it must have been intended to
prevent ;-). (The Git feature that does address that use case
is the `.git/info/exclude` file.)
0 commit comments