From: Greg Kurz <groug@kaod.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Christian Schoenebeck <qemu_oss@crudebyte.com>,
QEMU Developers <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: Tue, 23 Feb 2021 12:39:43 +0100 [thread overview]
Message-ID: <20210223123943.06d23a56@bahia.lan> (raw)
In-Reply-To: <CAFEAcA8x6GnfaHtfTLtEMiM1Xm9K7dhsMEpFjf2MFYe7T1jF4w@mail.gmail.com>
On Tue, 23 Feb 2021 11:09:05 +0000
Peter Maydell <peter.maydell@linaro.org> wrote:
> On Mon, 22 Feb 2021 at 14:43, Greg Kurz <groug@kaod.org> wrote:
> > My understanding is that users must be "maintainer" to edit other's
> > patches. Only three 'maintainers' are currently listed at ozlabs for
> > QEMU:
> >
> > https://patchwork.ozlabs.org/api/1.0/projects/14/
> >
> > We had a discussion about that a few months back with Christian Schoenebeck
> > (9pfs maintainer, Cc'd) who also uses patchworks. It turned out we didn't
> > quite know how to go further because of lack of documentation, but I'd be
> > glad to experiment the full patchwork experience if someone knows how to
> > do it :-)
>
> If people want to try that kind of thing out I'm happy to try
> to tweak their permissions on the patchwork instance.
>
Please do for me then. My name is groug :)
Cheers,
--
Greg
> -- PMM
next prev parent reply other threads:[~2021-02-23 11:40 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 [this message]
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
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=20210223123943.06d23a56@bahia.lan \
--to=groug@kaod.org \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--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 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.