[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1J5ecS-0008UX-00@gondolin.me.apana.org.au>
Date: Fri, 21 Dec 2007 17:56:40 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: alan@...rguk.ukuu.org.uk (Alan Cox)
Cc: joe@...ches.com, davem@...emloft.net, apw@...dowen.org,
lizf@...fujitsu.com, akpm@...ux-foundation.org, elendil@...net.nl,
linux-kernel@...r.kernel.org, tglx@...utronix.de,
trivial@...nel.org, rdunlap@...otime.net, jschopp@...tin.ibm.com
Subject: Re: Trailing periods in kernel messages
Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
>
> I do not believe "opinions" are relevant here. Relevant would be cites
> from respected style guides (Fowlers, Oxford Guide To Style et al.) to
> show they do not need a full stop.
>
> I've not found one, but I am open to references.
Well from where I come from, full stops are only used for complete
sentences. For example,
http://www.ballarat.edu.au/aasp/student/learning_support/generalguide/ch01s05s02.shtml
As to what is a complete sentence, that is debatable. However,
typically it would include a subject and a predicate. By this
rule the following line is not a complete sentence:
[XFS] Initialise current offset in xfs_file_readdir correctly
The reason is that it lacks a subject.
Of course I would completely agree that some kernel messages
are complete sentences and should have a full stop. However,
it is not clear to me that this is the case for all or even
most kernel printk messages.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists