qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Michael.Kang" <blackfin.kang@gmail.com>
Cc: QEMU Development <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Is it the time to split the current qemu-devel maillist
Date: Mon, 30 Jun 2014 17:07:01 +0200	[thread overview]
Message-ID: <20140630150701.GD10229@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CA+QCq15rZcx-EuhKg9pu_SfbXv3+8kNGcco-MYEYLgPtYFT85Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 719 bytes --]

On Thu, Jun 26, 2014 at 10:33:11AM +0800, Michael.Kang wrote:
> It looks a lot of mail related to patch commit flood the current
> maillist every day. It is hard to find some RFC or the useful
> discussions. Especially, some patch sets are only related to some
> specific
> target.

Patch emails are not commit notifications.  They are requests for others
to review code before it can be merged.  Without code review we cannot
merge code, so it's pretty important and definitely "useful".  *More*
attention to patch review would help rather than *less*.

Anyway, what is the concrete suggestion?  A qemu-patches@nongnu.org
mailing list to separate patches from other development discussions like
bugs and RFCs?

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2014-06-30 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26  2:33 [Qemu-devel] Is it the time to split the current qemu-devel maillist Michael.Kang
2014-06-30 15:07 ` Stefan Hajnoczi [this message]

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=20140630150701.GD10229@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=blackfin.kang@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).