From: Jeremy Kerr <jk@ozlabs.org>
To: Greg Kurz <groug@kaod.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Christian Schoenebeck <qemu_oss@crudebyte.com>,
qemu-devel@nongnu.org,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: who's using the ozlabs patchwork install for QEMU patches ?
Date: Thu, 25 Feb 2021 21:04:42 +0800 [thread overview]
Message-ID: <ac5c0acbed14c415314b67fe5b99f89e2d5e067c.camel@ozlabs.org> (raw)
In-Reply-To: <20210224092020.269ab775@bahia.lan>
Hi Greg,
> > The standard process is to send me an email :)
>
> Is this standard process mentioned somewhere ?
No, not really. I usually let the folks who request the project in the
first place know though.
> > You're wanting to add user 'groug' to the qemu project, is that
> > correct?
> >
>
> Yes. Thanks !
Sure thing, done!
You should now have access to modify patch states in the qemu
patchwork. If you'd prefer to work with patchwork from the command-
line, check out the pwclient, git-pw and pwnm-sync tools, at:
https://patchwork.readthedocs.io/en/latest/usage/clients/
Cheers,
Jeremy
next prev parent reply other threads:[~2021-02-25 13:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 16:26 who's using the ozlabs patchwork install for QEMU patches ? Peter Maydell
2021-02-19 16:51 ` Thomas Huth
2021-02-20 8:19 ` David Gibson
2021-02-22 7:21 ` Greg Kurz
2021-02-22 13:59 ` Peter Maydell
2021-02-22 14:43 ` Greg Kurz
2021-02-23 6:57 ` Bin Meng
2021-02-23 9:55 ` Greg Kurz
2021-02-23 10:24 ` Bin Meng
2021-02-23 11:09 ` Peter Maydell
2021-02-23 11:39 ` Greg Kurz
2021-02-23 11:54 ` Peter Maydell
2021-02-23 12:24 ` Christian Schoenebeck
2021-02-23 12:40 ` Alexey Kardashevskiy
2021-02-24 0:29 ` Jeremy Kerr
2021-02-24 8:20 ` Greg Kurz
2021-02-25 13:04 ` Jeremy Kerr [this message]
2021-02-19 18:07 ` BALATON Zoltan
2021-02-19 18:27 ` Philippe Mathieu-Daudé
2021-02-20 9:14 ` Bin Meng
2021-02-20 11:51 ` Alex Bennée
2021-02-21 16:40 ` Warner Losh
2021-02-22 7:49 ` Cédric Le Goater
2021-02-24 9:04 ` Gerd Hoffmann
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=ac5c0acbed14c415314b67fe5b99f89e2d5e067c.camel@ozlabs.org \
--to=jk@ozlabs.org \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--cc=sfr@canb.auug.org.au \
--cc=thuth@redhat.com \
/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).