From: Andrew Lunn <andrew@lunn.ch>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH net] docs: netdev: document the existence of the mail bot
Date: Tue, 23 May 2023 03:46:46 +0200 [thread overview]
Message-ID: <043df418-28f0-49e5-bff0-2ea511148bb6@lunn.ch> (raw)
In-Reply-To: <20230522230903.1853151-1-kuba@kernel.org>
On Mon, May 22, 2023 at 04:09:03PM -0700, Jakub Kicinski wrote:
> We had a good run, but after 4 weeks of use we heard someone
> asking about pw-bot commands. Let's explain its existence
> in the docs. It's not a complete documentation but hopefully
> it's enough for the casual contributor. The project and scope
> are in flux so the details would likely become out of date,
> if we were to document more in depth.
>
> Link: https://lore.kernel.org/all/20230522140057.GB18381@nucnuc.mle/
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> +Instead of delegating patchwork permissions netdev uses a simple mail
> +bot which looks for special commands/lines within the emails sent to
> +the mailing list. For example to mark a series as Changes Requested
> +one needs to send the following line anywhere in the email thread::
> +
> + pw-bot: changes-requested
...
> + https://patchwork.hopto.org/pw-bot.html
[Evil grin]
So your patch did not trigger the bot. Lets see if my reply does?
[/Evil grin]
Andrew
next prev parent reply other threads:[~2023-05-23 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 23:09 [PATCH net] docs: netdev: document the existence of the mail bot Jakub Kicinski
2023-05-23 1:46 ` Andrew Lunn [this message]
2023-05-23 2:05 ` Jakub Kicinski
2023-05-24 7:14 ` Martin Habets
2023-05-23 10:49 ` Simon Horman
2023-05-24 4:20 ` patchwork-bot+netdevbpf
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=043df418-28f0-49e5-bff0-2ea511148bb6@lunn.ch \
--to=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.