workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>, workflows@vger.kernel.org
Subject: Re: Monitoring the status of your own patches on patchwork?
Date: Tue, 14 Dec 2021 09:31:37 -0700	[thread overview]
Message-ID: <CAPnjgZ0t6TyUM4YYeSiVB3CQKzCq3k+5LZn7R26Oi9WwCxmX=A@mail.gmail.com> (raw)
In-Reply-To: <1919dc6e-66b7-4179-7991-cbae44215c1f@infradead.org>

Hi Randy,

On Mon, 13 Dec 2021 at 19:12, Randy Dunlap <rdunlap@infradead.org> wrote:
>
>
>
> On 12/13/21 10:37, Simon Glass wrote:
> > 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.
> >
> > I would like something that can track all the series and tell me what
> > is outstanding. At the moment I keep a manual list but often forget
> > things.
>
> Hi,
> Where is this 'patman' found, please?
>
> I see   https://source.denx.de/u-boot/custodians/u-boot-dm/-/tree/patman-working
> and   https://github.com/siemens/u-boot/tree/master/tools/patman
> (the latter one seems to be untouched recently).
>
> Is there another URL or is the denx.de URL the one to use?

You can use Denx but I suggest github:

https://github.com/u-boot/u-boot

I should figure out how to get patman into pip.

Regards,
Simon

      reply	other threads:[~2021-12-14 16:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-11 19:06 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
2021-12-13 23:51     ` Simon Glass
2021-12-14  2:12   ` Randy Dunlap
2021-12-14 16:31     ` Simon Glass [this message]

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='CAPnjgZ0t6TyUM4YYeSiVB3CQKzCq3k+5LZn7R26Oi9WwCxmX=A@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=rdunlap@infradead.org \
    --cc=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