> -----Original Message----- > From: Konstantin Ryabitsev <konstan...@linuxfoundation.org> > Sent: Wednesday, February 17, 2021 4:24 PM > To: Ali Alnubani <alia...@nvidia.com> > Cc: patchwork@lists.ozlabs.org; NBU-Contact-Thomas Monjalon > <tho...@monjalon.net> > Subject: Re: Autodelegation based on more complex rules > > On Wed, Feb 17, 2021 at 02:15:23PM +0000, Ali Alnubani wrote: > > > I suggest that you do this outside of patchwork, using procmail and > filtering > > > hooks to set X-Patchwork-Delegate. This is what we do at kernel.org, > though > > > we > > > don't directly parse the MAINTAINERS file. You can see our scripts here: > > > > > > https://git.kernel.org/pub/scm/infra/patchwork/procmail.git/tree/ > > > > > > > Thanks for the suggestion, If I understand your configurations correctly, > > they don't consider the hierarchy of trees though (e.g., when submitters > > change files in multiple trees), do they? > > No, because we don't have a reason to do so. Moreover, I'm not sure how it > would work, as a submission can only be delegated to a single > person/account. > If a patch touches multiple files, you still have to pick a single delegate.
Right, but shouldn't that delegate be the maintainer of a tree that is higher in the hierarchy rather than a maintainer of one of the subtrees maintaining each of these files separately? - Ali _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
