From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LxnNw-0008GS-VM
	for qemu-devel@nongnu.org; Sat, 25 Apr 2009 15:18:00 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LxnNv-0008G8-IT
	for qemu-devel@nongnu.org; Sat, 25 Apr 2009 15:18:00 -0400
Received: from [199.232.76.173] (port=35992 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LxnNv-0008G5-DT
	for qemu-devel@nongnu.org; Sat, 25 Apr 2009 15:17:59 -0400
Received: from naru.obs2.net ([84.20.150.76]:60458)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <nchip@kos.to>) id 1LxnNv-0006L4-4F
	for qemu-devel@nongnu.org; Sat, 25 Apr 2009 15:17:59 -0400
Date: Sat, 25 Apr 2009 22:17:56 +0300
From: Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] QEMU git tree is now activate
Message-ID: <20090425191756.GA19344@kos.to>
References: <49F1EAB5.1060703@us.ibm.com> <49F235F1.80807@us.ibm.com>
	<20090425152612.GA6584@kos.to> <49F331F9.2030308@us.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49F331F9.2030308@us.ibm.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

On Sat, Apr 25, 2009 at 10:53:29AM -0500, Anthony Liguori wrote:
> Riku Voipio wrote:
>> It seems the git commits don't get posted to this mailing list anymore.
>> Is that the purpose? I think the svn commit messages were usefull.

> They go to qemu-commits@nongnu.org now.  The thinking is that it's  
> easier for people interested in commits to subscribe to that list and  
> filter those messages into the same bucket as qemu-devel than it is for  
> folks that aren't interested in these messages to filter them out.

> I can certainly direct them to qemu-devel if there is agreement that  
> that's where we want them to go.

Separate list is ok for me. If the development process of qemu
gets faster and the pace of commits increases, separate list is almost
mandatory. There was just no news about this side effect of git
transition.