qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-s390x <qemu-s390x@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Process] QEMU submaintainers and pull requests
Date: Fri, 16 Feb 2018 17:09:04 +0100	[thread overview]
Message-ID: <20180216170904.5933125f.cohuck@redhat.com> (raw)
In-Reply-To: <4a71adf2-f617-74c2-cf7e-34517ac6aade@redhat.com>

On Fri, 16 Feb 2018 16:08:39 +0100
Paolo Bonzini <pbonzini@redhat.com> wrote:

> On 16/02/2018 16:03, Peter Maydell wrote:
> > On 16 February 2018 at 14:53, Paolo Bonzini <pbonzini@redhat.com> wrote:  
> >> On 16/02/2018 12:25, Peter Maydell wrote:  
> >>> On 16 February 2018 at 11:18, Cornelia Huck <cohuck@redhat.com> wrote:
> >>> The block folks are already doing this, so we should just
> >>> formalize what they're doing at the moment I guess. From my point
> >>> of view as long as there's something I can easily filter
> >>> in/out in the email body or subject so I don't get confused
> >>> (and which doesn't require me to update my filters every time
> >>> a new subsystem switches to using submaintainer pulls!)
> >>> I don't mind about the rest of it. Maybe a subject line with
> >>> 'PULL SUBSYSTEM s390x' (ditto block, etc etc) ?  
> >>
> >> What about just requiring you to be in the "To" or "Cc" fields?  That
> >> works pretty well for Linux.  
> > 
> > It would require existing submaintainers to change their process,
> > though -- currently not all pull requests are to/cc me.  
> 
> Yeah, but that would not be too hard.  There are only about 40
> maintainers, and if anybody misses the news they would notice fairly
> quickly. :)

Well, I wouldn't mind (I send pull requests to Peter anyway, and I'd
certainly want s390x pull requests addressed to me as well).

We could use both (subject prefix and To:/Cc:) for a
belt-and-suspenders approach.

> 
> BTW, Fam and I are also planning to improve Patchew so that it is better
> at detecting pull requests and especially merged pull requests.

Cool.

Would a certain formatting be helpful for patchew as well? Or do you
plan to parse the cover letter to hopefully find the output of git
request-pull and get the correct base from that?

  reply	other threads:[~2018-02-16 16:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 11:18 [Qemu-devel] [Process] QEMU submaintainers and pull requests Cornelia Huck
2018-02-16 11:25 ` Peter Maydell
2018-02-16 12:28   ` Cornelia Huck
2018-02-16 14:53   ` Paolo Bonzini
2018-02-16 15:03     ` Peter Maydell
2018-02-16 15:08       ` Paolo Bonzini
2018-02-16 16:09         ` Cornelia Huck [this message]
2018-02-17  8:51           ` Paolo Bonzini
2018-02-16 15:13       ` Daniel P. Berrangé
2018-02-16 15:26         ` Peter Maydell

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=20180216170904.5933125f.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    /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).