From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Simon Glass <sjg@chromium.org>
Cc: workflows@vger.kernel.org
Subject: Re: Monitoring the status of your own patches on patchwork?
Date: Mon, 13 Dec 2021 22:43:26 +0100 [thread overview]
Message-ID: <87r1agyydd.fsf@toke.dk> (raw)
In-Reply-To: <CAPnjgZ1THJQSUj2Mmq2P6EtJXZQV=th0vnN2cLZ=BZe_sck+SA@mail.gmail.com>
Simon Glass <sjg@chromium.org> writes:
> Hi,
>
> On Sat, 11 Dec 2021 at 12:06, Toke Høiland-Jørgensen <toke@redhat.com> 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?
>>
>> 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 :)
>
> I'll just mention 'patman status' here, which collects tags from
> patchwork so you can send them with the next version. It also shows
> you code-review snippets on the cmdline which I find much faster to
> process, particularly for large patches. See below, although it's a
> bit hard to read without the colours that patman uses.
Ah, this is cool, didn't know about patman! Will take a closer look, it
seems to be solving some of the same issues I've been rolling my own
solutions for - thanks for the pointer! :)
-Toke
next prev parent reply other threads:[~2021-12-13 21:43 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
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 [this message]
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=87r1agyydd.fsf@toke.dk \
--to=toke@redhat.com \
--cc=sjg@chromium.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 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.