From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58712) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WTAEu-00050x-4n for qemu-devel@nongnu.org; Thu, 27 Mar 2014 09:21:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WTAEm-0005jo-TR for qemu-devel@nongnu.org; Thu, 27 Mar 2014 09:21:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:15295) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WTAEm-0005jX-LV for qemu-devel@nongnu.org; Thu, 27 Mar 2014 09:20:52 -0400 Date: Thu, 27 Mar 2014 17:29:52 +0530 From: Amit Shah Message-ID: <20140327115719.GA24211@grmbl.mre> References: <20140327104930.GB27036@grmbl.mre> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PULL for-2.0] migration: add traces List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: qemu list , Anthony Liguori On (Thu) 27 Mar 2014 [11:18:05], Peter Maydell wrote: > On 27 March 2014 10:49, Amit Shah wrote: > > The following changes since commit db237e33c08a279f0179f8f5128a6d10d9adc38a: > > > > Merge remote-tracking branch 'remotes/riku/for-2.0' into staging (2014-03-26 17:10:16 +0000) > > > > are available in the git repository at: > > > > > > git://git.kernel.org/pub/scm/virt/qemu/amit/migration.git tags/for_upstream > > > > for you to fetch changes up to 9013dca5539186ddca018bebcf2d5da63d061365: > > > > migration: add more traces (2014-03-27 15:19:00 +0530) > > > > ---------------------------------------------------------------- > > migration: traces > > > > Adds trace messages to migration path. Patches have been on list for a > > while, and have been reviewed by Juan. > > > > ---------------------------------------------------------------- > > Alexey Kardashevskiy (2): > > util: add qemu_ether_ntoa > > migration: add more traces > > Really for 2.0? This seems more like a feature than a bugfix > to me... They've been on-list for 2.0, and the last time the 2nd patch didn't compile on windows, and hence was left out. The first patch was added to the series to fix that. Seems like a trivial couple of patches.. Amit