All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: Greg Kurz <groug@kaod.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	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 18:24:07 +0800	[thread overview]
Message-ID: <CAEUhbmWUMaf=vqKibc0fnHR+BJVyO2-mvg+rPXPdVSPGsCHUag@mail.gmail.com> (raw)
In-Reply-To: <20210223105510.0687d0b6@bahia.lan>

On Tue, Feb 23, 2021 at 5:55 PM Greg Kurz <groug@kaod.org> wrote:
>
> On Tue, 23 Feb 2021 14:57:21 +0800
> Bin Meng <bmeng.cn@gmail.com> wrote:
>
> > On Mon, Feb 22, 2021 at 10:43 PM Greg Kurz <groug@kaod.org> wrote:
> > >
> > > On Mon, 22 Feb 2021 13:59:34 +0000
> > > Peter Maydell <peter.maydell@linaro.org> wrote:
> > >
> > > > 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 ?
> > > >
> > >
> > > Only the latter but mostly because I don't have the permissions
> > > to change status, e.g. when trying to change status of this
> > > recent patch from Cedric to rearrange the PowerPC docs:
> > >
> > > You don't have permissions to edit patch 'docs/system: Extend PPC section'
> > >
> > > My understanding is that users must be "maintainer" to edit other's
> > > patches. Only three 'maintainers' are currently listed at ozlabs for
> > > QEMU:
> >
> > I can update my patch status in the QEMU project. I am not sure if
> > this is due to I am a maintainer of another project hosted on
> > ozlabs.org.
> >
>
> Yeah everyone can update its own patches but you need to
> be maintainer of a project to update the status of other's
> patch for this project IIUC.
>

Ah, I see, thanks. So the question is whether QEMU maintainers want to
try the practice of using patchwork to help their maintenance work ...

> > >
> > > 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 :-)
> >
> > I personally found patchwork is really helpful for mainatiner's work.
> > But it looks the maintainers from the QEMU community do not use it.

Regards,
Bin


  reply	other threads:[~2021-02-23 10:27 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 [this message]
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='CAEUhbmWUMaf=vqKibc0fnHR+BJVyO2-mvg+rPXPdVSPGsCHUag@mail.gmail.com' \
    --to=bmeng.cn@gmail.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=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.