From: Michael Tokarev <mjt@tls.msk.ru>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/2] docs/memory.txt: Put one whitespace between sentences
Date: Mon, 05 May 2014 15:05:49 +0400 [thread overview]
Message-ID: <5367708D.80803@msgid.tls.msk.ru> (raw)
In-Reply-To: <1399287591-6525-2-git-send-email-famz@redhat.com>
05.05.2014 14:59, Fam Zheng wrote:
> In other words, whitespace changes only.
> The memory API models the memory and I/O buses and controllers of a QEMU
> -machine. It attempts to allow modelling of:
> +machine. It attempts to allow modelling of:
What's the point? In text form, it is quite often and, to my taste, quite
normal to use 2 spaces after the full-dot (at the end of the sentence), just
like an extra line between paragraphs. This way, it is easier to separate
sentences between each other.
In real typography, 1.5-sized space is usually used in such places. But since
plaintext format has no 1.5-sized space, 2 spaces is used.
I'd send an opposite patch, which adds additional space where it is missing.. :)
Thanks,
/mjt
next prev parent reply other threads:[~2014-05-05 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 10:59 [Qemu-devel] [PATCH v2 0/2] docs/memory.txt: Fixes on whitespace and MMIO operations Fam Zheng
2014-05-05 10:59 ` [Qemu-devel] [PATCH v2 1/2] docs/memory.txt: Put one whitespace between sentences Fam Zheng
2014-05-05 11:05 ` Michael Tokarev [this message]
2014-05-05 11:30 ` Fam Zheng
2014-05-05 10:59 ` [Qemu-devel] [PATCH v2 2/2] docs/memory.txt: Fix document on MMIO operations Fam Zheng
2014-05-05 11:05 ` [Qemu-devel] [PATCH v2 0/2] docs/memory.txt: Fixes on whitespace and " Fam Zheng
2014-05-05 11:07 ` 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=5367708D.80803@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=famz@redhat.com \
--cc=pbonzini@redhat.com \
--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).