From: Peter Maydell <peter.maydell@linaro.org>
To: Jim Meyering <jim@meyering.net>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] fix some common typos
Date: Wed, 9 May 2012 15:48:27 +0100 [thread overview]
Message-ID: <CAFEAcA8-piOQNSZ_r9Rd7_-2UjBYnZm+cAu9WHo-nYbMCLO0Sg@mail.gmail.com> (raw)
In-Reply-To: <87y5p1wh42.fsf@rho.meyering.net>
On 9 May 2012 15:42, Jim Meyering <jim@meyering.net> wrote:
>
> These were identified using: http://github.com/lyda/misspell-check
> which I ran like this to create a bourne shell script using GNU sed's
> -i option:
>
> git ls-files|grep -vF .bin | misspellings -f - |grep -v '^ERROR:' |perl \
> -pe 's/^(.*?)\[(\d+)\]: (\w+) -> "(.*?)"$/sed -i '\''${2}s!$3!$4!'\'' $1/'
>
> Manually eliding the FP, "rela->real" and resolving "addres" to
> address (not "adders") we get this:
>
> sed -i '450s!thru!through!' Changelog
> sed -i '260s!neccessary!necessary!' coroutine-sigaltstack.c
> sed -i '54s!miniscule!minuscule!' disas.c
> sed -i '1094s!thru!through!' hw/usb/hcd-ehci.c
> sed -i '1095s!thru!through!' hw/usb/hcd-ehci.c
> sed -i '21s!unecessary!unnecessary!' qapi-schema-guest.json
> sed -i '307s!explictly!explicitly!' qemu-ga.c
> sed -i '490s!preceeding!preceding!' qga/commands-posix.c
> sed -i '792s!addres!address!' qga/commands-posix.c
> sed -i '6s!beeing!being!' tests/tcg/test-mmap.c
>
> Signed-off-by: Jim Meyering <meyering@redhat.com>
> ---
> Changelog | 2 +-
> coroutine-sigaltstack.c | 2 +-
> disas.c | 2 +-
> hw/usb/hcd-ehci.c | 4 ++--
> qapi-schema-guest.json | 2 +-
> qemu-ga.c | 2 +-
> qga/commands-posix.c | 4 ++--
> tests/tcg/test-mmap.c | 2 +-
> 8 files changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/Changelog b/Changelog
> index 8b63258..13eebef 100644
> --- a/Changelog
> +++ b/Changelog
> @@ -447,7 +447,7 @@ version 0.5.0:
> - multi-target build
> - fixed: no error code in hardware interrupts
> - fixed: pop ss, mov ss, x and sti disable hardware irqs for the next insn
> - - correct single stepping thru string operations
> + - correct single stepping through string operations
> - preliminary SPARC target support (Thomas M. Ogrisegg)
> - tun-fd option (Rusty Russell)
> - automatic IDE geometry detection
> diff --git a/coroutine-sigaltstack.c b/coroutine-sigaltstack.c
> index 7ff2d33..ddcb603 100644
> --- a/coroutine-sigaltstack.c
> +++ b/coroutine-sigaltstack.c
> @@ -257,7 +257,7 @@ static Coroutine *coroutine_new(void)
> /*
> * Now enter the trampoline again, but this time not as a signal
> * handler. Instead we jump into it directly. The functionally
> - * redundant ping-pong pointer arithmentic is neccessary to avoid
> + * redundant ping-pong pointer arithmentic is necessary to avoid
Also "arithmetic".
Otherwise OK.
-- PMM
next prev parent reply other threads:[~2012-05-09 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 14:42 [Qemu-trivial] [PATCH] fix some common typos Jim Meyering
2012-05-09 14:48 ` Peter Maydell [this message]
2012-05-09 15:12 ` [Qemu-trivial] [PATCHv2] " Jim Meyering
2012-05-09 15:13 ` Peter Maydell
2012-05-14 20:38 ` [Qemu-trivial] [Qemu-devel] " Stefan Weil
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=CAFEAcA8-piOQNSZ_r9Rd7_-2UjBYnZm+cAu9WHo-nYbMCLO0Sg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=jim@meyering.net \
--cc=patches@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).