From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
joe@perches.com, davem@davemloft.net, apw@shadowen.org,
lizf@cn.fujitsu.com, akpm@linux-foundation.org,
elendil@planet.nl, linux-kernel@vger.kernel.org,
tglx@linutronix.de, trivial@kernel.org, rdunlap@xenotime.net,
jschopp@austin.ibm.com
Subject: Re: Trailing periods in kernel messages
Date: Fri, 21 Dec 2007 11:01:25 -0500 [thread overview]
Message-ID: <20071221160125.GJ2310@csclub.uwaterloo.ca> (raw)
In-Reply-To: <Pine.LNX.4.64.0712211254160.21721@fbirervta.pbzchgretzou.qr>
On Fri, Dec 21, 2007 at 12:55:16PM +0100, Jan Engelhardt wrote:
> o_O I better continue believing it is the subject. Because with
> one extra word at the front, you can make this a "complete sentence":
>
> Please initialize [the] current offset in xfs_file_readdir.
That still looks like an incomplete sentence, although orders are often
given in that form. Something like these seem more like complete
sentences:
You should initialize the current offset in xfs_file_readdir.
The driver will now initialize the current offset in xfs_file_readdir.
Where you or the driver is the subject. Then it makes sense. Of course
one would tend to assume the driver is just giving status reports so it
implicitly is the subject doing the things, even though there is no
actual sentence saying so.
It is more of the driver saying:
this driver is:
initializing the current offset in xfs_file_readdir
doing some other stuff
then doing some different stuff
etc
--
Len Sorensen
next prev parent reply other threads:[~2007-12-21 16:01 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 7:35 [PATCH 6/6] tick: add a missing dot in prink Li Zefan
2007-11-29 8:58 ` Frans Pop
2007-11-29 9:29 ` Li Zefan
2007-11-29 10:20 ` Trailing periods in kernel messages (was: [PATCH 6/6] tick: add a missing dot in prink) Frans Pop
2007-11-29 11:20 ` Andrew Morton
2007-11-30 1:12 ` Trailing periods in kernel messages Li Zefan
2007-11-30 1:30 ` Joe Perches
2007-11-30 1:54 ` Li Zefan
2007-11-30 2:35 ` Joe Perches
2007-12-20 16:29 ` Andy Whitcroft
2007-12-20 21:07 ` Alan Cox
2007-12-20 21:43 ` Joe Perches
2007-12-20 21:54 ` Alan Cox
2007-12-20 22:19 ` Andrew Morton
2007-12-20 22:34 ` Randy Dunlap
2007-12-20 23:40 ` Alan Cox
2007-12-20 22:22 ` Theodore Tso
2007-12-20 23:38 ` Alan Cox
2007-12-21 15:54 ` Lennart Sorensen
2007-12-20 21:51 ` David Miller
2007-12-20 22:07 ` Joe Perches
2007-12-20 22:08 ` Alan Cox
2007-12-20 23:14 ` J.A. Magallón
2007-12-21 0:04 ` Joe Perches
2007-12-21 0:40 ` Alan Cox
2007-12-21 9:56 ` Herbert Xu
2007-12-21 10:10 ` Jan Engelhardt
2007-12-21 10:12 ` David Miller
2007-12-21 13:43 ` David Newall
2007-12-21 14:01 ` David Miller
2007-12-21 15:37 ` David Newall
2007-12-21 11:41 ` Herbert Xu
2007-12-21 11:55 ` Jan Engelhardt
2007-12-21 16:01 ` Lennart Sorensen [this message]
2007-12-22 14:04 ` Benny Amorsen
2007-12-22 20:20 ` Radoslaw Szkodzinski
2007-12-21 12:06 ` David Schwartz
2007-12-21 15:18 ` Stefan Richter
2007-12-20 22:09 ` Roland Dreier
2007-12-21 1:43 ` Frans Pop
2007-12-21 2:15 ` Andrew Morton
2007-12-21 3:12 ` David Miller
2007-12-21 10:15 ` Jan Engelhardt
2007-12-21 10:21 ` Alan Cox
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=20071221160125.GJ2310@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=apw@shadowen.org \
--cc=davem@davemloft.net \
--cc=elendil@planet.nl \
--cc=herbert@gondor.apana.org.au \
--cc=jengelh@computergmbh.de \
--cc=joe@perches.com \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=rdunlap@xenotime.net \
--cc=tglx@linutronix.de \
--cc=trivial@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
all inboxes | Powered by JetHome®