From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MHfNf-0005xs-1z
	for qemu-devel@nongnu.org; Fri, 19 Jun 2009 10:47:51 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MHfNa-0005qa-7H
	for qemu-devel@nongnu.org; Fri, 19 Jun 2009 10:47:50 -0400
Received: from [199.232.76.173] (port=38807 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MHfNa-0005qK-1e
	for qemu-devel@nongnu.org; Fri, 19 Jun 2009 10:47:46 -0400
Received: from mx20.gnu.org ([199.232.41.8]:33422)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1MHfNZ-0004ml-BG
	for qemu-devel@nongnu.org; Fri, 19 Jun 2009 10:47:45 -0400
Received: from mail.codesourcery.com ([65.74.133.4])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1MHfNX-0001cP-Lv
	for qemu-devel@nongnu.org; Fri, 19 Jun 2009 10:47:43 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] sending pci information over the wire
Date: Fri, 19 Jun 2009 15:47:39 +0100
References: <20090618193946.GH3517@poweredge.glommer>
	<4A3B8E56.3040903@codemonkey.ws> <4A3BA1C6.6040701@redhat.com>
In-Reply-To: <4A3BA1C6.6040701@redhat.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200906191547.41173.paul@codesourcery.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: qemu-devel@nongnu.org
Cc: Glauber Costa <glommer@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>, armbru@redhat.com

>   Also it seems for merges only a message for the merge commit goes to
> the list, not for the individual patches.

This depends how the merge is done. A few of the recent merges did not rebase 
the changes before comitting. This leads to nonlinear revision history, as can 
easily be seen with e.g. .gitk e510e05b

Paul