From: Thomas Monjalon <thomas@monjalon.net>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"juraj.linkes@pantheon.tech" <juraj.linkes@pantheon.tech>
Subject: Re: [dpdk-ci] [PATCH v2 05/10] tools: add functionality for setting pw delegates
Date: Thu, 04 Nov 2021 19:16:29 +0100 [thread overview]
Message-ID: <2566422.rZZgpRVHQ4@thomas> (raw)
In-Reply-To: <CH0PR12MB51569D5EC14157441A322516DA8D9@CH0PR12MB5156.namprd12.prod.outlook.com>
04/11/2021 17:48, Ali Alnubani:
> From: Thomas Monjalon <thomas@monjalon.net>
> > 18/10/2021 09:48, Ali Alnubani:
> > > From: Thomas Monjalon <thomas@monjalon.net>
> > > > 21/09/2021 16:35, alialnu@nvidia.com:
> > > > > From: Ali Alnubani <alialnu@nvidia.com>
> > > > >
> > > > > A new command was added to set patch delegates in Patchwork
> > > > > based on the emails found in DPDK's MAINTAINERS file.
> > > > >
> > > > > Example usage:
> > > > > $ export MAINTAINERS_FILE_PATH=/path/to/dpdk/MAINTAINERS
> > > > > $ ./pw_maintainers_cli.py --type series set_pw_delegate SERIES_ID
> > > > >
> > > > > Signed-off-by: Ali Alnubani <alialnu@nvidia.com>
> > > > > ---
> > > > > + def set_delegate(self, patch_list, delegate):
> > > > > + """Set the delegate for a patch.
> > > > > + Only tries to set a delegate for patches that don't have
> > > > > + one set already.
> > > >
> > > > I'm not sure we should skip patches which are already delegated.
> > > > If we use the command to explicitly delegate the patch,
> > > > we should do it, right?
> > > >
> > > > The skip logic may be implemented at a higher level in the CI.
> > >
> > > I added an arg (--force_set_delegate) to force overriding delegates in v3.
> >
> > Given the command is to set delegate, the force looks strange to me.
> > Wouldn't it be more logical to add an option to skip already delegated
> > patches?
>
> Isn't it safer not to force overriding the delegate by default?
> Users can send patches with the header "X-Patchwork-Delegate" to set a specific delegate. Maintainers might want to set another user as the delegate when there are multiple delegates in the MAINTAINERS file for a patch. Should we override these by default?
These considerations don't contradict with the option name.
If we have the option --skip-delegated (or --only-non-delegated),
we can always use this option in the automatic run.
But for a manual run, I expect the script to delegate a patch
the user explicitly wants to set, without requiring a "force" option.
next prev parent reply other threads:[~2021-11-04 18:16 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 15:45 [dpdk-ci] [PATCH 0/9] Automatic patchwork delegation Ali Alnubani
2021-09-06 15:45 ` [dpdk-ci] [PATCH 1/9] tools: rename guess_git_tree script Ali Alnubani
2021-09-07 11:03 ` Juraj Linkeš
2021-09-08 16:54 ` Ali Alnubani
2021-09-06 15:45 ` [dpdk-ci] [PATCH 2/9] tools: match by tree url instead of tree name Ali Alnubani
2021-09-06 15:45 ` [dpdk-ci] [PATCH 3/9] tools: update script usage Ali Alnubani
2021-09-06 15:45 ` [dpdk-ci] [PATCH 4/9] tools: add functionality for detecting tree maintainers Ali Alnubani
2021-09-06 15:45 ` [dpdk-ci] [PATCH 5/9] tools: add functionality for setting pw delegates Ali Alnubani
2021-09-06 15:45 ` [dpdk-ci] [PATCH 6/9] add git-pw to requirements file Ali Alnubani
2021-09-06 15:45 ` [dpdk-ci] [PATCH 7/9] tools: filter new patchwork IDs by date Ali Alnubani
2021-09-06 15:58 ` Ali Alnubani
2021-09-06 15:45 ` [dpdk-ci] [PATCH 8/9] tools: add support for fetching new series IDs Ali Alnubani
2021-09-06 15:45 ` [dpdk-ci] [PATCH 9/9] tools: filter new patchwork IDs by project name Ali Alnubani
2021-09-21 14:35 ` [dpdk-ci] [PATCH v2 00/10] Automatic patchwork delegation alialnu
2021-09-21 14:35 ` [dpdk-ci] [PATCH v2 01/10] tools: rename guess_git_tree script alialnu
2021-09-21 14:35 ` [dpdk-ci] [PATCH v2 02/10] tools: match by tree url instead of tree name alialnu
2021-09-30 8:00 ` Thomas Monjalon
2021-10-18 7:48 ` Ali Alnubani
2021-09-21 14:35 ` [dpdk-ci] [PATCH v2 03/10] tools: update script usage alialnu
2021-09-30 8:09 ` Thomas Monjalon
2021-09-21 14:35 ` [dpdk-ci] [PATCH v2 04/10] tools: add functionality for detecting tree maintainers alialnu
2021-09-30 8:29 ` Thomas Monjalon
2021-09-21 14:35 ` [dpdk-ci] [PATCH v2 05/10] tools: add functionality for setting pw delegates alialnu
2021-09-30 9:15 ` Thomas Monjalon
2021-10-18 7:48 ` Ali Alnubani
2021-10-26 14:08 ` Thomas Monjalon
2021-11-04 16:48 ` Ali Alnubani
2021-11-04 18:16 ` Thomas Monjalon [this message]
2021-11-08 7:45 ` Ali Alnubani
2021-09-21 14:35 ` [dpdk-ci] [PATCH v2 06/10] add git-pw to requirements file alialnu
2021-09-21 14:35 ` [dpdk-ci] [PATCH v2 07/10] tools: filter new patchwork IDs by date alialnu
2021-10-11 20:08 ` Ali Alnubani
2021-09-21 14:35 ` [dpdk-ci] [PATCH v2 08/10] tools: add support for fetching new series IDs alialnu
2021-09-30 10:25 ` Thomas Monjalon
2021-09-21 14:35 ` [dpdk-ci] [PATCH v2 09/10] tools: filter new patchwork IDs by project name alialnu
2021-09-30 10:28 ` Thomas Monjalon
2021-09-21 14:35 ` [dpdk-ci] [PATCH v2 10/10] tools: skip the IDs we already fetched alialnu
2021-09-30 10:32 ` Thomas Monjalon
2021-10-11 19:30 ` Ali Alnubani
2021-10-12 6:44 ` Thomas Monjalon
2021-10-18 8:04 ` Ali Alnubani
2021-10-26 14:07 ` Thomas Monjalon
2021-11-04 16:53 ` Ali Alnubani
2021-11-04 18:08 ` Thomas Monjalon
2021-11-08 7:44 ` Ali Alnubani
2021-11-08 6:28 ` [dpdk-ci] [PATCH v4 00/10] Automatic patchwork delegation Ali Alnubani
2021-11-08 6:28 ` [dpdk-ci] [PATCH v4 01/10] tools: rename guess_git_tree script Ali Alnubani
2021-11-08 6:28 ` [dpdk-ci] [PATCH v4 02/10] tools: match by tree URL instead of tree name Ali Alnubani
2021-11-08 6:28 ` [dpdk-ci] [PATCH v4 03/10] tools: update script usage Ali Alnubani
2021-11-08 6:28 ` [dpdk-ci] [PATCH v4 04/10] tools: add functionality for detecting tree maintainers Ali Alnubani
2021-11-08 6:28 ` [dpdk-ci] [PATCH v4 05/10] tools: add functionality for setting pw delegates Ali Alnubani
2021-11-08 6:28 ` [dpdk-ci] [PATCH v4 06/10] add git-pw to requirements file Ali Alnubani
2021-11-08 6:28 ` [dpdk-ci] [PATCH v4 07/10] tools: filter new Patchwork IDs by date Ali Alnubani
2021-11-08 6:28 ` [dpdk-ci] [PATCH v4 08/10] tools: support fetching series Ali Alnubani
2021-11-08 6:28 ` [dpdk-ci] [PATCH v4 09/10] tools: filter new patchwork IDs by project name Ali Alnubani
2021-11-08 6:28 ` [dpdk-ci] [PATCH v4 10/10] tools: skip the IDs we already fetched Ali Alnubani
2022-01-05 1:05 ` [PATCH v4 00/10] Automatic patchwork delegation Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2566422.rZZgpRVHQ4@thomas \
--to=thomas@monjalon.net \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=juraj.linkes@pantheon.tech \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).