From: malc <av1474@comtv.ru>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: Blue Swirl <blauwirbel@gmail.com>, Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Unclear committer situation
Date: Wed, 2 Dec 2009 11:45:53 +0300 (MSK) [thread overview]
Message-ID: <Pine.LNX.4.64.0912021143150.3655@linmac.oyster.ru> (raw)
In-Reply-To: <20091202082612.GU2310@hall.aurel32.net>
On Wed, 2 Dec 2009, 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.
Just to clarify esp. taking into consideration first paragraph of
Alexander's message, i do not care one bit about PPC target (not
until Alexander does something magical with PPC64 and i can continue
trying to resolve an old Linux's hard lockup issue). I do care about
PPC the host though.
>
> 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.
>
>
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2009-12-02 8:45 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
2009-12-02 8:45 ` malc [this message]
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=Pine.LNX.4.64.0912021143150.3655@linmac.oyster.ru \
--to=av1474@comtv.ru \
--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).