From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: workflows@vger.kernel.org
Subject: Re: Monitoring the status of your own patches on patchwork?
Date: Mon, 13 Dec 2021 16:48:37 +0100 [thread overview]
Message-ID: <877dc8fqui.fsf@toke.dk> (raw)
In-Reply-To: <20211213070840.4353fd6d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Jakub Kicinski <kuba@kernel.org> writes:
> On Sat, 11 Dec 2021 20:06:00 +0100 Toke Høiland-Jørgensen wrote:
>> 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?
>
> Status notification when checks are failing? Hopefully not, we don't
> want people posting patches just to get them tested...
Well no, but sometimes a patch will have failures despite the best
efforts of the submitter (otherwise what's the point of the checks?).
Right now the only way for me to discover that there's an issue is to go
look at the patchwork web interface, and I wanted something that better
suits my workflow (i.e., that's not in a web browser).
I wasn't asking for patchwork to send out automatic notifications
(yikes!), I just wanted to know if anyone else had done something
similar before I go play around with the patchwork API myself... :)
-Toke
next prev parent reply other threads:[~2021-12-13 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 19:06 Monitoring the status of your own patches on patchwork? Toke Høiland-Jørgensen
2021-12-13 15:08 ` Jakub Kicinski
2021-12-13 15:48 ` Toke Høiland-Jørgensen [this message]
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=877dc8fqui.fsf@toke.dk \
--to=toke@redhat.com \
--cc=kuba@kernel.org \
--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 NNTP newsgroup(s).