qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Subject: [Qemu-devel] [PATCH v2] CODING_STYLE: Fix a typo ("have" vs. "has")
Date: Fri, 30 Sep 2016 02:04:28 +0200	[thread overview]
Message-ID: <20160930000428.22382-1-j.neuschaefer@gmx.net> (raw)
In-Reply-To: <20160929233847.n5xe7gmdb5ys5ujv@latitude>

Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>

---
v2:
- Preserve the poetic sound of "Many a flamewar", which Peter Maydell
  pointed out.
---
 CODING_STYLE | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CODING_STYLE b/CODING_STYLE
index e7fde15..f53180b 100644
--- a/CODING_STYLE
+++ b/CODING_STYLE
@@ -9,7 +9,7 @@ patches before submitting.
 Of course, the most important aspect in any coding style is whitespace.
 Crusty old coders who have trouble spotting the glasses on their noses
 can tell the difference between a tab and eight spaces from a distance
-of approximately fifteen parsecs.  Many a flamewar have been fought and
+of approximately fifteen parsecs.  Many a flamewar has been fought and
 lost on this issue.
 
 QEMU indents are four spaces.  Tabs are never used, except in Makefiles
-- 
2.9.3

  reply	other threads:[~2016-09-30  0:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 20:46 [Qemu-devel] [PATCH] CODING_STYLE: Fix a typo ("Many a flamewar") Jonathan Neuschäfer
2016-09-29 22:14 ` Peter Maydell
2016-09-29 23:38   ` Jonathan Neuschäfer
2016-09-30  0:04     ` Jonathan Neuschäfer [this message]
2016-09-30  0:29       ` [Qemu-devel] [PATCH v2] CODING_STYLE: Fix a typo ("have" vs. "has") Peter Maydell
2016-10-08  8:12       ` Michael Tokarev

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=20160930000428.22382-1-j.neuschaefer@gmx.net \
    --to=j.neuschaefer@gmx.net \
    --cc=peter.maydell@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).