All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Stefan Weil <sw@weilnetz.de>, Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] We need more reviewers/maintainers!!
Date: Tue, 13 Mar 2012 15:49:44 +0100	[thread overview]
Message-ID: <4F5F5E88.9040601@suse.de> (raw)
In-Reply-To: <4F5F50BF.2020107@redhat.com>

Am 13.03.2012 14:50, schrieb Avi Kivity:
> On 03/13/2012 11:09 AM, Peter Maydell wrote:
>>> If we start saying that, Alex "owns" ppc except for things that are
>>> "important" like a build breakage, then we get into the ugly definition of
>>> what's important and what's not important.
>>
>> I don't think we've had huge problems with defining "trivial" and I
>> don't think we'd really have big arguments about "urgent" either --
>> as the gatekeeper you and the other direct-committers can always use
>> your judgement and say 'this should go through the submaintainer tree'.
>>
>> I agree completely with Alex about why urgent fixes don't mesh well with
>> the periodic submaintainer tree pullreq workflow. Dumping the 'urgent'
>> fix problem off onto submaintainers is basically asking us all to
>> have an extra 'foo-urgent' tree and send out single patch pullreqs,
>> which seems to me like a very heavyweight way of causing a patch to
>> be applied 
> 
> 
> Not at all.  I have a memory/core branch and a memory/urgent branch --
> it's trivial to maintain them with git, and quite often I send a 1-patch
> pull request.  There's no material difference between sending a patch
> and sending a pull request (except if you use git.kernel.org, ugh), and
> it does guarantee you priority handing.

Actually there is: A trivial fix can be sent with a one-liner:

$ git send-email HEAD^

whereas there is no matching command for sending a pull request. You
need to manage your own scripts that place git-pull-request output into
the cover letter. (And quite obviously you need a publicly available git
repository in the first place. Most of us do by now.)

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  parent reply	other threads:[~2012-03-13 14:49 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 17:06 [Qemu-devel] We need more reviewers/maintainers!! Stefano Stabellini
2012-03-12 17:16 ` Anthony Liguori
2012-03-12 17:34   ` Stefano Stabellini
2012-03-12 18:48     ` Anthony Liguori
2012-03-12 19:10       ` Stefano Stabellini
2012-03-12 19:04         ` Anthony Liguori
2012-03-12 19:21           ` Stefano Stabellini
2012-03-12 19:38             ` Anthony Liguori
2012-03-13 11:34               ` Stefano Stabellini
2012-03-13 11:27     ` Kevin Wolf
2012-03-13 11:41       ` Stefano Stabellini
2012-03-13 12:12       ` Paolo Bonzini
2012-03-12 18:03 ` Lluís Vilanova
2012-03-12 18:10   ` Anthony Liguori
2012-03-12 19:39     ` Lluís Vilanova
2012-03-12 19:43       ` Anthony Liguori
2012-03-12 18:18   ` Stefano Stabellini
2012-03-13 13:27     ` Avi Kivity
2012-03-14 13:50       ` Andreas Färber
2012-03-14 13:52         ` Anthony Liguori
2012-03-14 13:58           ` Peter Maydell
2012-03-14 14:17             ` Anthony Liguori
2012-03-14 14:25               ` Andreas Färber
2012-03-13 10:38   ` Andreas Färber
2012-03-12 19:18 ` Michael Roth
2012-03-13 11:11   ` Stefano Stabellini
2012-03-12 20:12 ` Stefan Weil
2012-03-12 20:24   ` Peter Maydell
2012-03-12 20:29     ` Anthony Liguori
2012-03-12 20:43       ` Peter Maydell
2012-03-12 21:06         ` Anthony Liguori
2012-03-12 21:09           ` malc
2012-03-12 21:13             ` Anthony Liguori
2012-03-12 21:41               ` Stefan Weil
2012-03-12 21:52                 ` Anthony Liguori
2012-03-12 21:43               ` malc
2012-03-12 21:49                 ` Anthony Liguori
2012-03-12 22:53                   ` malc
2012-03-12 21:16           ` Peter Maydell
2012-03-12 21:19             ` Anthony Liguori
2012-03-13 10:39         ` Stefan Hajnoczi
2012-03-12 20:40     ` Michael S. Tsirkin
2012-03-12 20:27   ` Anthony Liguori
2012-03-12 21:12     ` Stefan Weil
2012-03-12 21:18       ` Anthony Liguori
2012-03-12 23:32         ` Andreas Färber
2012-03-13  0:16           ` Anthony Liguori
2012-03-13  0:54             ` Alexander Graf
2012-03-13  1:01             ` Andreas Färber
2012-03-13  1:23               ` Alexander Graf
2012-03-13  1:31                 ` Super Bisquit
2012-03-13  1:39                 ` Anthony Liguori
2012-03-13  2:04                   ` Alexander Graf
2012-03-13  2:05                     ` Anthony Liguori
2012-03-14 19:47               ` Blue Swirl
2012-03-13  9:09             ` Peter Maydell
2012-03-13 13:50               ` Avi Kivity
2012-03-13 14:12                 ` Peter Maydell
2012-03-13 14:39                   ` Avi Kivity
2012-03-13 14:43                     ` Anthony Liguori
2012-03-13 14:46                       ` Alexander Graf
2012-03-13 14:54                       ` Peter Maydell
2012-03-13 14:49                 ` Andreas Färber [this message]
2012-03-13 14:57                   ` Avi Kivity
2012-03-13 15:13                     ` Eric Blake
2012-03-12 21:24     ` Stefan Weil
2012-03-13 13:40     ` Avi Kivity
2012-03-13 14:00       ` Anthony Liguori
2012-03-13 14:38         ` Avi Kivity
2012-03-13 14:41           ` Anthony Liguori
2012-03-14 20:00             ` Blue Swirl
2012-03-14 19:55       ` Blue Swirl
2012-03-13 10:41   ` Stefan Hajnoczi
2012-03-13 16:31     ` Andreas Färber
2012-03-13 18:14       ` Stefan Weil
2012-03-14  9:17         ` Stefan Hajnoczi
2012-07-18  9:28   ` 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=4F5F5E88.9040601@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=sw@weilnetz.de \
    /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.