From: David Newall <david@davidnewall.com>
To: David Miller <davem@davemloft.net>
Cc: jengelh@computergmbh.de, herbert@gondor.apana.org.au,
alan@lxorguk.ukuu.org.uk, joe@perches.com, 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: Sat, 22 Dec 2007 02:07:05 +1030 [thread overview]
Message-ID: <476BDDA1.4040302@davidnewall.com> (raw)
In-Reply-To: <20071221.060125.165132180.davem@davemloft.net>
David Miller wrote:
> From: David Newall <david@davidnewall.com>
> Date: Sat, 22 Dec 2007 00:13:07 +1030
>> David Miller wrote:
>>
>>> From: Jan Engelhardt <jengelh@computergmbh.de>
>>> Date: Fri, 21 Dec 2007 11:10:38 +0100 (CET)
>>>
>>>
>>>> Can we get back to programming?
>>>>
>> With respect to the vast majority of log messages, nobody confounded by
>> punctuation is truly trying to analyze a problem!
>>
>
> And nobody confounded by whitespace and coding style is truly
> interesting in writing properly functioning code!
>
I supposed you meant "interested." Proper coding style doesn't make for
proper code. Arguably, it aids when reading code, and that's why we
mostly stick to agreed standards; but it's hard to get worked up over a
dot at the end of a log message. In cases where it really does matter,
we make sure it's right; but demanding that every message meets some
unilateral idea of what is right is zealotry.
next prev parent reply other threads:[~2007-12-21 15:37 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 [this message]
2007-12-21 11:41 ` Herbert Xu
2007-12-21 11:55 ` Jan Engelhardt
2007-12-21 16:01 ` Lennart Sorensen
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=476BDDA1.4040302@davidnewall.com \
--to=david@davidnewall.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.