From: Tommy Reynolds <Tommy.Reynolds@MegaCoder.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Bug zapper? :)
Date: Mon, 9 Aug 2004 20:55:02 -0500 [thread overview]
Message-ID: <20040809205502.62bec992.Tommy.Reynolds@MegaCoder.com> (raw)
In-Reply-To: <E1BuKyX-0005hJ-00@calista.eckenfels.6bone.ka-ip.net>
Uttered Bernd Eckenfels <ecki-news2004-05@lina.inka.de>, spake thus:
> - no comments are better than wrong comments
> - code which is understandable w/o comments is better than commented code
Therefore, kernel code is better than wrong comments?
Just trying to complete the syllogism ;-)
next prev parent reply other threads:[~2004-08-10 1:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 20:07 [RFC] Bug zapper? :) John Richard Moser
[not found] ` <200408100042.37159.vda@port.imtp.ilyichevsk.odessa.ua>
2004-08-09 23:09 ` John Richard Moser
2004-08-10 0:58 ` Bernd Eckenfels
2004-08-10 1:55 ` Tommy Reynolds [this message]
2004-08-10 2:47 ` Rik van Riel
2004-08-10 3:13 ` John Richard Moser
2004-08-10 8:35 ` Jakob Oestergaard
2004-08-10 15:19 ` John Richard Moser
2004-08-10 21:43 ` Bernd Eckenfels
2004-08-10 21:30 ` V13
2004-08-10 23:35 ` John Richard Moser
2004-08-11 4:50 ` Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2004-08-10 21:13 Nick Warne
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=20040809205502.62bec992.Tommy.Reynolds@MegaCoder.com \
--to=tommy.reynolds@megacoder.com \
--cc=linux-kernel@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