From: Amit Shah <amit.shah@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu list <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PULL for-2.0] migration: add traces
Date: Thu, 27 Mar 2014 17:29:52 +0530 [thread overview]
Message-ID: <20140327115719.GA24211@grmbl.mre> (raw)
In-Reply-To: <CAFEAcA8_KBa=Fx69FV9OLoTWrezjO_r-50LTCojLZ-CHqU6ohw@mail.gmail.com>
On (Thu) 27 Mar 2014 [11:18:05], Peter Maydell wrote:
> On 27 March 2014 10:49, Amit Shah <amit.shah@redhat.com> 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
next prev parent reply other threads:[~2014-03-27 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 10:49 [Qemu-devel] [PULL for-2.0] migration: add traces Amit Shah
2014-03-27 11:18 ` Peter Maydell
2014-03-27 11:59 ` Amit Shah [this message]
2014-03-27 15:31 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140327115719.GA24211@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).