From: Peter Maydell <peter.maydell@linaro.org>
To: Greg Kurz <groug@kaod.org>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Thomas Huth <thuth@redhat.com>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: who's using the ozlabs patchwork install for QEMU patches ?
Date: Mon, 22 Feb 2021 13:59:34 +0000 [thread overview]
Message-ID: <CAFEAcA8oqPR=PbqWaoBGfDKWik6Jv5TuE-PZqTc0W3TsoktvsA@mail.gmail.com> (raw)
In-Reply-To: <20210222082137.1b3f8b3b@bahia.lan>
On Mon, 22 Feb 2021 at 07:21, Greg Kurz <groug@kaod.org> wrote:
>
> On Fri, 19 Feb 2021 17:51:02 +0100
> Thomas Huth <thuth@redhat.com> wrote:
>
> > On 19/02/2021 17.26, Peter Maydell wrote:
> > > Does anybody use the ozlabs patchwork install for QEMU patches,
> > > either occasionally or on a regular basis ?
> > > http://patchwork.ozlabs.org/project/qemu-devel/list/
> > > The admins for that system are trying to identify which of
> > > the various projects are really using their patchwork instances,
> > > so I figured I'd do a quick survey here. We don't use it
> > > as an official project tool but it's certainly possible to
> > > use it as an individual developer in one way or another.
> >
> > I think it might be used by some of the ppc hackers ... so CC:-ing to
> > qemu-pcc ...
> >
>
> I do on a very regular basis.
Thanks for the reports. Do you use the features like assigning
patches to people and changing patch status, or do you mostly
just use it as a read-only archive-of-patches ?
-- PMM
next prev parent reply other threads:[~2021-02-22 14:03 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 [this message]
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
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='CAFEAcA8oqPR=PbqWaoBGfDKWik6Jv5TuE-PZqTc0W3TsoktvsA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.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 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).