From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PULL 0/1] Tracing patches
Date: Fri, 18 Nov 2016 15:33:09 +0000 [thread overview]
Message-ID: <20161118153309.GA3266@stefanha-x1.localdomain> (raw)
In-Reply-To: <1479481289-2479-1-git-send-email-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On Fri, Nov 18, 2016 at 03:01:28PM +0000, Stefan Hajnoczi wrote:
> The following changes since commit b0bcc86d2a87456f5a276f941dc775b265b309cf:
>
> Update version for v2.8.0-rc0 release (2016-11-15 20:55:12 +0000)
>
> are available in the git repository at:
>
> git://github.com/stefanha/qemu.git tags/tracing-pull-request
>
> for you to fetch changes up to d4f7ca59017835784c6872dfab0e269d9b41b05a:
>
> trace: fix generated code build break (2016-11-18 11:09:58 +0000)
>
> ----------------------------------------------------------------
>
> ----------------------------------------------------------------
>
> Greg Kurz (1):
> trace: fix generated code build break
>
> scripts/tracetool.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --
> 2.7.4
>
>
Thanks, applied to my staging tree:
https://github.com/stefanha/qemu/commits/staging
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-11-18 15:33 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 15:01 [Qemu-devel] [PULL 0/1] Tracing patches Stefan Hajnoczi
2016-11-18 15:01 ` [Qemu-devel] [PULL 1/1] trace: fix generated code build break Stefan Hajnoczi
2016-11-18 15:33 ` Stefan Hajnoczi [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-27 20:33 [Qemu-devel] [PULL 0/1] Tracing patches Stefan Hajnoczi
2019-09-03 13:03 ` Peter Maydell
2019-04-29 16:10 Stefan Hajnoczi
2019-04-29 16:10 ` Stefan Hajnoczi
2019-04-30 9:20 ` Peter Maydell
2019-04-30 9:20 ` Peter Maydell
2019-04-30 23:08 ` no-reply
2019-04-30 23:08 ` no-reply
2019-05-01 4:42 ` no-reply
2019-05-01 4:42 ` no-reply
2018-06-01 15:04 Stefan Hajnoczi
2018-06-01 16:12 ` Peter Maydell
2018-05-11 18:28 Stefan Hajnoczi
2018-05-14 12:15 ` Peter Maydell
2017-10-05 14:25 Stefan Hajnoczi
2017-10-05 16:28 ` Peter Maydell
2017-09-15 17:39 Stefan Hajnoczi
2017-09-16 13:35 ` Peter Maydell
2017-08-07 11:04 Stefan Hajnoczi
2017-08-07 13:14 ` Peter Maydell
2017-06-07 18:55 Stefan Hajnoczi
2017-06-12 14:29 ` Peter Maydell
2016-11-29 10:07 Stefan Hajnoczi
2016-11-29 10:21 ` Stefan Hajnoczi
2016-11-08 18:17 Stefan Hajnoczi
2016-11-09 12:44 ` Stefan Hajnoczi
2016-05-17 13:07 Stefan Hajnoczi
2016-05-17 13:46 ` Peter Maydell
2015-09-03 14:46 Stefan Hajnoczi
2015-09-03 16:27 ` Peter Maydell
2015-02-06 13:45 Stefan Hajnoczi
2015-02-06 14:35 ` Peter Maydell
2013-09-20 17:58 Stefan Hajnoczi
2013-09-20 20:40 ` Paolo Bonzini
2011-11-01 14:19 Stefan Hajnoczi
2011-11-01 18:13 ` Anthony Liguori
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=20161118153309.GA3266@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).