On Tue, 15 Aug 2023, Reinette Chatre wrote: > On 8/15/2023 2:10 AM, Ilpo Järvinen wrote: > >> ps. Unless you have an updated email address that works, could you please > >> remove Sai's email from future submissions? > > > > It's auto-added by git send-email machinery. I guess I can try to make > > an exception to my usual workflow by sending only to manually specified To > > addresses (if I remember). Perhaps one day I'll write a tool to filter out > > the addresses from git send-email generated ones but as is I don't have > > one. > > > > Which git send-email machinery are you referring to? If I understand correctly > it does not automatically pick addresses but you can provide custom commands to > it that can do it. Ah sorry, it is actually scripts/get_maintainer.pl automation I use with git send-email to figure out where to send the patches besides the --to & --cc entries I provided. For this patch, get_maintainer.pl returns this list: Fenghua Yu <fenghua.yu@xxxxxxxxx> (supporter:RDT - RESOURCE ALLOCATION,blamed_fixes:1/1=100%) Reinette Chatre <reinette.chatre@xxxxxxxxx> (supporter:RDT - RESOURCE ALLOCATION) Shuah Khan <shuah@xxxxxxxxxx> (maintainer:KERNEL SELFTEST FRAMEWORK,blamed_fixes:1/1=100%) Babu Moger <babu.moger@xxxxxxx> (blamed_fixes:1/1=100%) Sai Praneeth Prakhya <sai.praneeth.prakhya@xxxxxxxxx> (blamed_fixes:1/1=100%) linux-kernel@xxxxxxxxxxxxxxx (open list:RDT - RESOURCE ALLOCATION) linux-kselftest@xxxxxxxxxxxxxxx (open list:KERNEL SELFTEST FRAMEWORK) ...which includes Sai's address (not much I can do about that, it's immutably crafted into git history that those lines were once touched by Sai). I've thought of writing yet another wrapper to filter out known failing addresses but until that's done, either I need to (remember to) manually send the series w/o get_maintainer.pl automation or accept a few failures here and there. -- i.
