]> granicus.if.org Git - python/commit
bpo-37936: Avoid ignoring files that we actually do track. (GH-15451)
authorGreg Price <gnprice@gmail.com>
Mon, 9 Sep 2019 09:34:50 +0000 (02:34 -0700)
committerMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Mon, 9 Sep 2019 09:34:50 +0000 (02:34 -0700)
commit5e5e9515029f70836003a8cfb30433166fcc8db7
tree1e53ca7e10006ef1f133f7e0b011f4169acbf6fc
parente223ba13d8d871ee58570dfca4e82a591189cc2f
bpo-37936: Avoid ignoring files that we actually do track. (GH-15451)

There were about 14 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.

And the `Modules/Setup` rule simply wasn't updated after 961d54c5c.

https://bugs.python.org/issue37936
.gitignore
Misc/NEWS.d/next/Build/2019-08-24-00-29-40.bpo-37936.QrORqA.rst [new file with mode: 0644]