From: David Gibson <david@gibson.dropbear.id.au>
To: Thomas Huth <thuth@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Peter Maydell <peter.maydell@linaro.org>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: who's using the ozlabs patchwork install for QEMU patches ?
Date: Sat, 20 Feb 2021 19:19:36 +1100 [thread overview]
Message-ID: <YDDGGBfC4K62AtM7@yekko.fritz.box> (raw)
In-Reply-To: <99af17f9-10cf-7c9b-8222-2318b464f5b0@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
On Fri, Feb 19, 2021 at 05:51:02PM +0100, Thomas Huth 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 ...
Well, I'm not. TBH, I've never got the hang of patchwork.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-20 9:07 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 [this message]
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
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=YDDGGBfC4K62AtM7@yekko.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--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 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).