qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Lee Essen <lee.essen@nowonline.co.uk>
Cc: "Andreas Färber" <andreas.faerber@web.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix incorrect bracket in tracetool
Date: Mon, 19 Mar 2012 11:59:44 +0000	[thread overview]
Message-ID: <CAJSP0QXinWVd-Q-axG_8B1HzHapd2aiEXjfcyM14h47pxcZcsA@mail.gmail.com> (raw)
In-Reply-To: <541C8B7E-1E25-479E-B69E-A4B58BFA45F3@nowonline.co.uk>

On Fri, Mar 16, 2012 at 12:29 PM, Lee Essen <lee.essen@nowonline.co.uk> wrote:
> Signed-off-by: Lee Essen <lee.essen@nowonline.co.uk>
>
> ---
>
>  scripts/tracetool |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

I'm going to spend some time today reviewing recent tracing patches.
I'd prefer to move to a Python version of tracetool rather than worry
about the shell quirks across all host platforms.

If the Python rewrite cannot be merged for 1.1 then it makes sense to
go with shell portability fix.

Stefan

  parent reply	other threads:[~2012-03-19 12:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 12:29 [Qemu-devel] [PATCH] fix incorrect bracket in tracetool Lee Essen
2012-03-16 12:44 ` Andreas Färber
2012-03-16 13:00   ` Lee Essen
2012-03-16 13:19     ` Paolo Bonzini
2012-03-16 13:28       ` Andreas Färber
2012-03-16 13:21     ` Andreas Färber
2012-03-16 13:18 ` Paolo Bonzini
2012-03-16 14:56   ` Eric Blake
2012-03-19 11:59 ` Stefan Hajnoczi [this message]
2012-03-19 12:05   ` Lee Essen
2012-03-19 12:32     ` Stefan Hajnoczi
2012-03-19 12:32     ` Andreas Färber
2012-03-19 13:35       ` Lee Essen
2012-03-20 16:59         ` Stefan Hajnoczi
2012-03-20 17:11           ` Lee Essen
2012-03-21  9:52             ` Stefan Hajnoczi
2012-03-19 12:40     ` Stefan Weil
2012-03-19 12:49       ` Andreas Färber

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=CAJSP0QXinWVd-Q-axG_8B1HzHapd2aiEXjfcyM14h47pxcZcsA@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=andreas.faerber@web.de \
    --cc=lee.essen@nowonline.co.uk \
    --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).