From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] Unclear committer situation
Date: Wed, 02 Dec 2009 11:08:55 +0200 [thread overview]
Message-ID: <4B162EA7.4090601@redhat.com> (raw)
In-Reply-To: <FCDD64D4-0E73-4744-93E5-315AA72A2F03@suse.de>
On 12/02/2009 10:37 AM, Alexander Graf wrote:
> On 02.12.2009, at 09:26, Aurelien Jarno wrote:
>
>
>> On Tue, Dec 01, 2009 at 12:47:36PM +0100, Alexander Graf wrote:
>>
>>> Hi,
>>>
>>> Could someone with commit rights please stand up to feel responsible for
>>> PPC?
>>>
>>> Usually, when I send a patch to qemu-devel, I know who to address to
>>> increase chances of it getting committed. For kvm/vnc/block I just CC
>>> Anthony, for Audio I just CC malc, etc.
>>>
>>> There are some subsystems where nobody feels responsible though,
>>> apparently hoping 'someone else' will tske on it. Well, turns out it
>>> doesn't work that way.
>>>
>>> So could we please assign a committer for every subsystem around? Even
>>> if the committer doesn't know the architecture inside out, it's still
>>> valuable to have soneone feel responsible at all. Committer and
>>> maintainer also don't have to be the same person. I'll gladly maintain
>>> S390 without having commit rights - as long as I have someone to CC and
>>> know the patches will get merged.
>>>
>>>
>> I also try to follow the ppc architecture, though less than mips and
>> also depending on my free time. I know that Blue Swirl and Malc also
>> care about it.
>>
> Right - which makes it pretty hard. IMHO it's always best to have a single person to talk to when it comes to committing and others who comment on patches.
>
> In fact, I even believe that the person committing stuff doesn't have to know the stuff he commits. If I make a patch that breaks S390 and someone commits it, it's my fault breaking it - not the committer's. If I do a patch breaking PPC KVM, it's my fault breaking it, not the committer's. And with fault I also mean "responsibility to fix".
>
Breakage is simple. This difficult stuff is keeping the code maintainable.
>
>> It's not impossible that I miss patches given the current patches rate
>> on the mailing list, so don't hesitate to Cc: me. On the other hand, I
>> don't really feel comfortable with KVM related patches, I would prefer
>> to see them committed by Anthony.
>>
> Avi, can I get PPC KVM patches in through you then? I guess you're the closest person to the code in question.
>
Sure.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-12-02 9:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 11:47 [Qemu-devel] Unclear committer situation Alexander Graf
2009-12-01 18:51 ` Anthony Liguori
2009-12-01 19:21 ` Blue Swirl
2009-12-01 21:08 ` Anthony Liguori
2009-12-01 22:49 ` Alexander Graf
2009-12-02 11:18 ` andrzej zaborowski
2009-12-02 11:24 ` Alexander Graf
2009-12-02 12:38 ` Avi Kivity
2009-12-02 11:31 ` Riku Voipio
2009-12-03 14:04 ` Anthony Liguori
2009-12-02 8:26 ` Aurelien Jarno
2009-12-02 8:37 ` Alexander Graf
2009-12-02 8:46 ` Aurelien Jarno
2009-12-02 8:54 ` Alexander Graf
2009-12-02 21:09 ` Jan-Simon Möller
2009-12-02 9:08 ` Avi Kivity [this message]
2009-12-02 8:45 ` malc
2009-12-02 15:33 ` Artyom Tarasenko
2009-12-02 18:31 ` [Qemu-devel] " Jan Kiszka
2009-12-02 18:48 ` Artyom Tarasenko
2009-12-03 10:20 ` Michael S. Tsirkin
2009-12-03 13:10 ` andrzej zaborowski
2009-12-02 21:18 ` Anthony Liguori
2009-12-03 10:07 ` Artyom Tarasenko
2009-12-02 18:40 ` [Qemu-devel] " Anthony Liguori
2009-12-02 18:53 ` Artyom Tarasenko
2009-12-02 18:56 ` Alexander Graf
2009-12-03 9:44 ` Filip Navara
2009-12-03 14:19 ` Anthony Liguori
2009-12-02 19:12 ` Anthony Liguori
2009-12-03 9:20 ` Riku Voipio
2009-12-03 12:56 ` Carl-Daniel Hailfinger
2009-12-03 14:40 ` [Qemu-devel] " Michael S. Tsirkin
2009-12-05 0:25 ` [Qemu-devel] " Isaku Yamahata
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=4B162EA7.4090601@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@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).