From: Blue Swirl <blauwirbel@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tcg: fix typo in readme
Date: Sun, 9 Jan 2011 21:03:12 +0000 [thread overview]
Message-ID: <AANLkTimqrKTNhunf2TCMOTrFmvUbMoT=sq1a2w2RDtdb@mail.gmail.com> (raw)
In-Reply-To: <1294562745-19668-1-git-send-email-vapier@gentoo.org>
Thanks, applied.
On Sun, Jan 9, 2011 at 8:45 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
> tcg/README | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/tcg/README b/tcg/README
> index 68d27ff..8ec6845 100644
> --- a/tcg/README
> +++ b/tcg/README
> @@ -364,7 +364,7 @@ formed from two 32-bit arguments. The result is a 32-bit value.
>
> ********* QEMU specific operations
>
> -* tb_exit t0
> +* exit_tb t0
>
> Exit the current TB and return the value t0 (word type).
>
> --
> 1.7.4.rc1
>
>
>
prev parent reply other threads:[~2011-01-09 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 8:45 [Qemu-devel] [PATCH] tcg: fix typo in readme Mike Frysinger
2011-01-09 21:03 ` 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='AANLkTimqrKTNhunf2TCMOTrFmvUbMoT=sq1a2w2RDtdb@mail.gmail.com' \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=vapier@gentoo.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).