]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
bpo-37936: Avoid ignoring files that we actually do track. (GH-15451) (GH-15748)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Mon, 9 Sep 2019 13:10:19 +0000 (06:10 -0700)
committerZachary Ware <zachary.ware@gmail.com>
Mon, 9 Sep 2019 13:10:19 +0000 (08:10 -0500)
commit9ae9ac1061c76d637ebe9c1d6c6c802311d6ddba
tree693510636de5cc4febe46d3a0090d23e8f50712f
parent58a7f809ac978ed54034b7b48f2ea64000aa4661
bpo-37936: Avoid ignoring files that we actually do track. (GH-15451) (GH-15748)

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.

https://bugs.python.org/issue37936
(cherry picked from commit 5e5e9515029f70836003a8cfb30433166fcc8db7)

Authored-by: Greg Price <gnprice@gmail.com>
.gitignore
Misc/NEWS.d/next/Build/2019-08-24-00-29-40.bpo-37936.QrORqA.rst [new file with mode: 0644]