So we never intended to ignore all changes from the top-level down in /include
or /cachegrind. Instead allow the filetype-specific .gitignore patterns match
to the contents of these two folders.
Also, don't ignore changes to include/valgrind.h as it exists in the repository
and should be tracked for any changes developers might make.
Changes tested by running a git clean force and then full rebuild. No stray
build artifacts were being tracked erroneously by git after these changes.
/autom4te-*.cache
/autom4te.cache
/bin
-/cachegrind
/cachegrind.out.*
/compile
/config.guess
/default.supp
/depcomp
/glibc-2.X.supp
-/include
/install-sh
/lib
/Makefile
/include/Makefile.in
/include/Makefile
/include/tool.h
-/include/valgrind.h
/include/vgversion.h
# /include/vki/