On Tue, Sep 01, 2020 at 08:01:30AM +0200, Jan Beulich wrote: > I'm aware, and hence I said "aim for". In cases like this what we > often do is adjust things incrementally, as lines get touched anyway. > Of course if you want to clean it up all in one go ...
What I've got has turned into a patch series. There are some general .gitignore cleanup patches, followed by large mechanical fixes. Who should be included as Cc for submitting these? Usual pattern would end up including all the general maintainers on all patches. The reason is several of these are taking pieces off of the top-level .gitignore and moving those to subdirectory .gitignore files which would have shorter Cc lists. There wouldn't be actual effects at the top-level, merely those subdirectories. Should only the maintainers for the subdirectories be Cc'd? These also have limited testing. The testing which is possible is to simply run `git check-ignore -vn <filename>` and I'm lacking appropriate testers. I'm hopeful I'll get it right, but there is always that sweaty palms moment worrying I severely goof'd... -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
