qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] kqemu: merge CONFIG_KQEMU and USE_KQEMU
Date: Sun, 19 Apr 2009 13:18:36 +0300	[thread overview]
Message-ID: <f43fc5580904190318i5b762bcfxd5942f9d962394ee@mail.gmail.com> (raw)
In-Reply-To: <1240091515.21280.9.camel@x41.thuisdomein>

On 4/19/09, Paul Bolle <pebolle@tiscali.nl> wrote:
> Basically a recursive ":%s/USE_KQEMU/CONFIG_KQEMU/g".
>
>  Signed-off-by: Paul Bolle <pebolle@tiscali.nl>

Thanks, applied.

      reply	other threads:[~2009-04-19 10:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-18 11:54 [Qemu-devel] [PATCH] kqemu: only compile kqemu.o if actually needed Paul Bolle
2009-04-18 19:26 ` Blue Swirl
2009-04-18 21:51   ` [Qemu-devel] [PATCH] kqemu: merge CONFIG_KQEMU and USE_KQEMU Paul Bolle
2009-04-19 10:18     ` Blue Swirl [this message]

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=f43fc5580904190318i5b762bcfxd5942f9d962394ee@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=pebolle@tiscali.nl \
    --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).