From: Brian Norris <computersforpeace@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] A way to change the status of the whole series on Patchwork ?
Date: Wed, 23 Jul 2014 22:20:14 -0700 [thread overview]
Message-ID: <20140724052014.GI23883@brian-ubuntu> (raw)
In-Reply-To: <1406103008.27009.88.camel@dagon.hellion.org.uk>
On Wed, Jul 23, 2014 at 09:10:08AM +0100, Ian Campbell wrote:
> On Tue, 2014-07-22 at 12:45 -0700, Brian Norris wrote:
>
> > Then some sort of grepping/regex/etc. can get you the patchwork ID from
> > the Message-ID. e.g.:
> >
> > pwclient list -m "$MESSAGEID" | awk '{print $1;}' | grep '[0-9][0-9]*'
>
> Which version of pwclient do you use?
I was using the version from about a month ago (before the .pwclientrc
changes), pulled from ozlabs.org. It matches the client from
patchwork.git commit 5ccc2d9900f691ac6e3000836d052f60e0d1e726.
> The one from
> http://patchwork.ozlabs.org/help/pwclient/ doesn't support -m.
I just tried it. It worked for me...
No comment on the other compatibility questions. I'm aware of the
.pwclientrc / pwclient changes, but I haven't noticed them affect my
work (after converting my .pwclientrc). I don't use 'delegate' though.
Regards,
Brian
next prev parent reply other threads:[~2014-07-24 5:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 2:19 [U-Boot] A way to change the status of the whole series on Patchwork ? Masahiro Yamada
2014-07-17 2:49 ` Brian Norris
2014-07-22 2:37 ` Masahiro Yamada
2014-07-22 2:52 ` Brian Norris
2014-07-23 2:56 ` Masahiro Yamada
2014-07-22 13:50 ` Tom Rini
2014-07-22 19:45 ` Brian Norris
2014-07-23 8:10 ` Ian Campbell
2014-07-24 5:20 ` Brian Norris [this message]
2014-07-24 8:23 ` Ian Campbell
2014-07-24 7:23 ` Andreas Bießmann
2014-07-24 8:24 ` Ian Campbell
2014-07-24 8:28 ` Andreas Bießmann
2014-07-24 8:39 ` Ian Campbell
2014-07-24 8:38 ` Ian Campbell
2014-07-24 5:19 ` Masahiro Yamada
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=20140724052014.GI23883@brian-ubuntu \
--to=computersforpeace@gmail.com \
--cc=u-boot@lists.denx.de \
/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.