From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: workflows@vger.kernel.org
Subject: Monitoring the status of your own patches on patchwork?
Date: Sat, 11 Dec 2021 20:06:00 +0100 [thread overview]
Message-ID: <87mtl7ufl3.fsf@toke.dk> (raw)
Hi everyone!
I was wondering if anyone had any nifty tricks or utilities to help
monitor the status of your own patch submissions on a patchwork
instance? Things like getting a notification when a patch changes status
or when one of the automated checks on that particular patchwork
instance fails for a patch you submitted?
I can just filter the patchwork web interface to my name, of course, but
I would like something that can be automated so I can make the stuff I
care about show up in my inbox :)
Many thanks in advance!
-Toke
next reply other threads:[~2021-12-11 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 19:06 Toke Høiland-Jørgensen [this message]
2021-12-13 15:08 ` Monitoring the status of your own patches on patchwork? Jakub Kicinski
2021-12-13 15:48 ` Toke Høiland-Jørgensen
2021-12-13 16:06 ` Jakub Kicinski
2021-12-13 18:39 ` Toke Høiland-Jørgensen
2021-12-13 22:56 ` Kees Cook
2021-12-13 18:37 ` Simon Glass
2021-12-13 21:43 ` Toke Høiland-Jørgensen
2021-12-13 23:51 ` Simon Glass
2021-12-14 2:12 ` Randy Dunlap
2021-12-14 16:31 ` Simon Glass
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=87mtl7ufl3.fsf@toke.dk \
--to=toke@redhat.com \
--cc=workflows@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).