From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3] btrfs-progs: Doc: Add warning and note on btrfs-convert.
Date: Fri, 3 Apr 2015 08:33:23 +0000 (UTC) [thread overview]
Message-ID: <pan$e0c2f$781ca278$7c4e0058$da80a306@cox.net> (raw)
In-Reply-To: 551E3C06.9040305@cn.fujitsu.com
Qu Wenruo posted on Fri, 03 Apr 2015 15:06:46 +0800 as excerpted:
> It seems my English is really poor... :(
I think the usual response is "Better than my Chinese!" =:^)
Seriously, tho, it's better than many native English speakers/writers as
well, good enough I'd not guess different were it not for the name and
the cn hint in your email address. Meanwhile, while it was a sentence
fragment, in less formal settings (such as this list) it would have
passed more or less unnoticed, particularly since the meaning was so
obvious that not even a word needed changed, only a bit of punctuation.
In more formal setting such as btrfs documentation, however, a sentence
fragment of that sort will trigger the reader's misparse detector, thus
causing them to pause and go back and reread, slower, to see where their
natural parsing went wrong. As such, it brings attention to something
that would otherwise be fairly minor. So better to fix it now and not
have all those people stumbling over it later. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-04-03 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 1:21 [PATCH v3] btrfs-progs: Doc: Add warning and note on btrfs-convert Qu Wenruo
2015-04-03 5:55 ` Duncan
2015-04-03 7:06 ` Qu Wenruo
2015-04-03 7:16 ` Roman Mamedov
2015-04-03 9:56 ` Duncan
2015-04-03 8:33 ` Duncan [this message]
2015-04-07 15:04 ` David Sterba
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='pan$e0c2f$781ca278$7c4e0058$da80a306@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.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