From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52482) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X1dAl-0004af-Hp for qemu-devel@nongnu.org; Mon, 30 Jun 2014 11:07:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X1dAf-0006z3-JU for qemu-devel@nongnu.org; Mon, 30 Jun 2014 11:07:11 -0400 Received: from mail-we0-x233.google.com ([2a00:1450:400c:c03::233]:62600) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X1dAf-0006yx-Aw for qemu-devel@nongnu.org; Mon, 30 Jun 2014 11:07:05 -0400 Received: by mail-we0-f179.google.com with SMTP id w62so8152984wes.24 for ; Mon, 30 Jun 2014 08:07:04 -0700 (PDT) Date: Mon, 30 Jun 2014 17:07:01 +0200 From: Stefan Hajnoczi Message-ID: <20140630150701.GD10229@stefanha-thinkpad.redhat.com> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9dgjiU4MmWPVapMU" Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] Is it the time to split the current qemu-devel maillist List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael.Kang" Cc: QEMU Development --9dgjiU4MmWPVapMU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 --9dgjiU4MmWPVapMU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJTsX0VAAoJEJykq7OBq3PIsjAIAJt0hjYyY0J3THM6K5Det5Gs yfcz5LJR9EsEarTLDex6fzP7gN9djU/6R01u8FWF/ckVJRbdXne2bVtG2Luxt1XQ HdzCbLoQjrahhYjuO6XSL2UecYI/1mx+iPgrXOHflWzcKFgVTURQHUJjmfTjmWG4 v/ihVQ9bY3Eiq6fcpZo7qEjVQKxpWqFDgpsAWZk3wgG0J+oh24YuEKbzsu6UO6rV 3oebl0As5k+LjmcGrt2TALdX9TMOqjVzx6PIbm7Hc3l/WHrebGwn6mFn+QI5S+pc KYmliELzqIbzost/TJUNnmv4XDN1u7q9xSqBfCRj7Uv2Oa7+4jctQV/B945AiGs= =vXyE -----END PGP SIGNATURE----- --9dgjiU4MmWPVapMU--