Quoting Christophe JAILLET (2019-07-22 15:00:24) > > I don't use it explicitly, but the suggestions I get include some git > history, so I guess that it is on by default. > > I was thinking at parsing files to see if MODULE_AUTHOR includes an email. > Ok. Feel free to write a patch. Just know that MODULE_AUTHOR isn't always there so it's not a substitute for looking at git history or git blame to figure out who wrote the code. I suspect it's better to try to work on code and infrastructure to make these sorts of patches and questions irrelevant by detecting these problems before the code is merged, instead of after, by trawling the mailing lists and trying to apply patches and test them for common problems and then notifying the people working on the code. I don't have unlimited time in my life, so getting patches like this just makes me spend more time doing mundane tasks I don't want to do. TL;DR: Please help automate this sort of stuff!
