From: Luiz Capitulino <lcapitulino@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEMU patch management
Date: Thu, 10 Sep 2009 09:29:38 -0300 [thread overview]
Message-ID: <20090910092938.431a3622@doriath> (raw)
In-Reply-To: <20090910120121.GB27014@amit-x200.redhat.com>
On Thu, 10 Sep 2009 17:31:21 +0530
Amit Shah <amit.shah@redhat.com> wrote:
> On (Thu) Sep 10 2009 [08:47:13], Luiz Capitulino wrote:
> > On Thu, 10 Sep 2009 15:38:04 +0530
> > Amit Shah <amit.shah@redhat.com> wrote:
> >
> > > > - URL of staging tree
> > >
> > > Might help; but various developers might have their own staging trees
> > > (as it now is). If things change in the future, this will have to be
> > > modified.
> >
> > I think he's talking about Anthony's staging, which is the most
> > important one for those submitting patches.
>
> Right; and what I mean is like Anthony has his own queue, others might
> have theirs too. If something along the lines of what Avi suggested
> (having branches in the qemu repo for staging) gets implemented, this
> will have to be redone.
Yes, the point is: if we have a central tree where patches are
merged before going to master, the address of that tree should be
listed somewhere.
> > I might be wrong about this but, the Linux kernel way of having
> > people maintaining subsystems didn't work out here yet.
>
> It can easily be done. The process has to scale considering the number
> of submissions we're seeing.
I agree, with more maintainers QEMU would evolve a lot faster and I think
this is becoming an issue.
On the other hand I don't think we will have them by distributing
responsibilities, those interested should setup a tree and
start collecting patches.
next prev parent reply other threads:[~2009-09-10 12:29 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 7:49 [Qemu-devel] [PATCH] [RESEND] RTC polling mode broken Bernhard Kauer
2009-09-09 12:18 ` [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? Bernhard Kauer
2009-09-09 12:23 ` Amit Shah
2009-09-09 12:58 ` Bernhard Kauer
2009-09-09 12:25 ` Kevin Wolf
2009-09-09 13:00 ` Anthony Liguori
2009-09-09 13:26 ` Gleb Natapov
2009-09-09 13:45 ` Anthony Liguori
2009-09-09 14:31 ` Avi Kivity
2009-09-09 13:34 ` Bernhard Kauer
2009-09-10 7:03 ` Amit Shah
2009-09-10 7:56 ` Reimar Döffinger
2009-09-10 10:08 ` Amit Shah
2009-09-10 11:47 ` Luiz Capitulino
2009-09-10 12:01 ` [Qemu-devel] QEMU patch management Amit Shah
2009-09-10 12:29 ` Luiz Capitulino [this message]
2009-09-10 12:51 ` [Qemu-devel] " Reimar Döffinger
2009-09-10 13:11 ` Luiz Capitulino
2009-09-10 17:24 ` Reimar Döffinger
2009-09-10 13:58 ` [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? Anthony Liguori
2009-09-10 13:56 ` Anthony Liguori
2009-09-10 14:04 ` Amit Shah
2009-09-10 14:12 ` Anthony Liguori
2009-09-10 15:15 ` Amit Shah
2009-09-10 14:38 ` Avi Kivity
2009-09-10 15:54 ` Anthony Liguori
2009-09-10 16:09 ` Avi Kivity
2009-09-10 16:22 ` Anthony Liguori
2009-09-10 16:35 ` Avi Kivity
2009-09-10 16:38 ` Anthony Liguori
2009-09-10 16:46 ` Avi Kivity
2009-09-10 17:19 ` Reimar Döffinger
2009-09-11 12:39 ` Amit Shah
2009-09-12 5:55 ` Blue Swirl
2009-09-13 15:44 ` Avi Kivity
2009-09-13 16:30 ` Blue Swirl
2009-09-11 7:06 ` Gerd Hoffmann
2009-09-10 18:29 ` Mark McLoughlin
2009-09-10 18:40 ` Avi Kivity
2009-09-10 19:31 ` Anthony Liguori
2009-09-13 15:49 ` Avi Kivity
2009-09-10 20:36 ` Mark McLoughlin
2009-09-13 16:19 ` Avi Kivity
2009-09-14 7:49 ` Mark McLoughlin
2009-09-14 7:59 ` Avi Kivity
2009-09-10 18:59 ` Reimar Döffinger
2009-09-10 16:05 ` Anthony Liguori
2009-09-10 16:14 ` Avi Kivity
2009-09-11 9:16 ` [Qemu-devel] commit e09a5267 (was: [PATCH] [RESEND2] Qemu unmaintained?) Jan Kiszka
2009-09-11 12:56 ` [Qemu-devel] Re: commit e09a5267 Anthony Liguori
2009-09-11 13:04 ` Jan Kiszka
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=20090910092938.431a3622@doriath \
--to=lcapitulino@redhat.com \
--cc=amit.shah@redhat.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).