From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix two typos
Date: Tue, 26 Jun 2007 19:25:33 +0200 [thread overview]
Message-ID: <20070626172533.GD4096@aon.at> (raw)
In-Reply-To: <46814AB9.8080901@mail.berlios.de>
On Tue, Jun 26, 2007 at 07:19:53PM +0200, Stefan Weil wrote:
>Hi,
>
>here is another patch which changes additionnal -> additional.
>Please apply this new patch and my last one to CVS HEAD.
A few others, fwiw:
s/recieve/receive/g
s/seperat/separat/g
/[[:space:]]teh[[:space:]]/ the /g
cheers,
next prev parent reply other threads:[~2007-06-26 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 22:25 [Qemu-devel] [PATCH] Fix two typos Aurelien Jarno
2007-06-23 21:01 ` Stefan Weil
2007-06-26 17:19 ` Stefan Weil
2007-06-26 17:25 ` Bernhard Fischer [this message]
2007-06-26 20:23 ` Stefan Weil
2007-06-26 21:35 ` Jonathan Kalbfeld
2007-06-26 21:42 ` andrzej zaborowski
2007-07-03 19:28 ` Chris Wilson
2007-07-03 19:48 ` Jason Gress
2007-07-03 20:35 ` Stefan Weil
2007-07-02 18:48 ` Stuart Brady
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=20070626172533.GD4096@aon.at \
--to=rep.dot.nop@gmail.com \
--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).