From: Martin Habets <habetsm.xilinx@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
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: Wed, 24 May 2023 08:14:11 +0100 [thread overview]
Message-ID: <ZG25QxZ3hP5JCuqx@gmail.com> (raw)
In-Reply-To: <20230522190515.2793193f@kernel.org>
On Mon, May 22, 2023 at 07:05:15PM -0700, Jakub Kicinski wrote:
> On Tue, 23 May 2023 03:46:46 +0200 Andrew Lunn wrote:
> > > +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]
>
> Commands must be on separate lines, with no extra white space.
> I wonder if that proves the documentation is insufficient :)
I did wonder if the space before pw-bot was mandatory as well,
but apparently not.
Good improvement, thanks for documenting this.
Martin
next prev parent reply other threads:[~2023-05-24 7:14 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
2023-05-23 2:05 ` Jakub Kicinski
2023-05-24 7:14 ` Martin Habets [this message]
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=ZG25QxZ3hP5JCuqx@gmail.com \
--to=habetsm.xilinx@gmail.com \
--cc=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 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).