From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Greg Kurz <groug@kaod.org>, Thomas Huth <thuth@redhat.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
"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 13:24:30 +0100 [thread overview]
Message-ID: <2915273.dLz0rCdnKo@silver> (raw)
In-Reply-To: <CAFEAcA9mgE5t5KpkGac7ABaVy3gK11PbpNMfO3p-gcVhSN51tQ@mail.gmail.com>
On Dienstag, 23. Februar 2021 12:54:47 CET Peter Maydell wrote:
> On Tue, 23 Feb 2021 at 11:39, Greg Kurz <groug@kaod.org> wrote:
> > 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 :)
>
> Hmm. Having looked through the UI and docs I can't figure
> out how to do that (or even if 'maintainer' permission is
> sufficient to add other maintainers; maybe one has to ask the
> patchwork instance admins to do that?). If you can tell me what
> I need to do to add you to the maintainer list for QEMU I'll do it :-)
>
> -- PMM
We were looking into this last year, and from my (poor) understanding this is
how it works:
https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg02864.html
If somebody knows a more convenient/appropriate way, that would be
appreciated.
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2021-02-23 12:26 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 [this message]
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=2915273.dLz0rCdnKo@silver \
--to=qemu_oss@crudebyte.com \
--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=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.