From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43436) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WMrzz-0006Gv-Jx for qemu-devel@nongnu.org; Mon, 10 Mar 2014 00:39:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WMrzo-0006Tn-2w for qemu-devel@nongnu.org; Mon, 10 Mar 2014 00:39:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:17549) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WMrzn-0006TR-SZ for qemu-devel@nongnu.org; Mon, 10 Mar 2014 00:39:24 -0400 Date: Mon, 10 Mar 2014 10:09:04 +0530 From: Amit Shah Message-ID: <20140310043904.GA24543@grmbl.mre> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PULL] migration patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Alexey Kardashevskiy , Markus Armbruster , qemu list , Juan Quintela Hi Peter, On (Sat) 08 Mar 2014 [12:19:10], Peter Maydell wrote: > On 6 March 2014 20:03, Amit Shah wrote: > > Hi Juan, > > > > Here's a compilation of migration-related patches from the list that > > I've reviewed. > > > > For the first patch, I picked Markus's over yours, just because it's > > been on the list longer. > > > > > > The following changes since commit 9fbee91a131a05e443d7108d7fbdf3ca91020290: > > > > Merge remote-tracking branch 'remotes/kvm/uq/master' into staging (2014-02-27 16:00:31 +0000) > > > > are available in the git repository at: > > > > > > git://git.kernel.org/pub/scm/virt/qemu/amit/migration.git for-quintela > > Just for clarity: I'm assuming from the salutation and the branch name > that you're expecting Juan to merge these into his tree; I'm not > going to apply them to master. Yes, indeed, that was the case for this pull request. I intend to review a few migration patches on the list and send them on to Juan for review and later merging. If they're trivial, I'll pass them on to you directly. Should I mark the subject line as [migration PULL], so you don't have to bother with the pull req? Something else? Amit