From: Paul Jackson <pj@sgi.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: reiser@namesys.com, hch@infradead.org, akpm@osdl.org,
linux-kernel@vger.kernel.org, Reiserfs-Dev@namesys.com,
reiserfs-list@namesys.com, edward@namesys.com
Subject: Re: List of things requested by lkml for reiser4 inclusion (to review)
Date: Sat, 10 Sep 2005 00:28:51 -0700 [thread overview]
Message-ID: <20050910002851.5b984fde.pj@sgi.com> (raw)
In-Reply-To: <5FDA2C74-F923-4695-A1B8-4355D445C073@mac.com>
Kyle wrote:
> Sometimes cleverness can be even worse than ordinary abuse
I have a habit of commenting the code spots where it is not obvious
what is going on.
Someday I am going to learn that everytime I feel the compulsion
to write a "Watch out !" or "Beware !" or "Must !" code comment,
it probably means that I am coding crap.
I usually end up ripping out the code, after some bug has whacked
my upside the head.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2005-09-10 7:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200509091817.39726.zam@namesys.com>
2005-09-09 17:36 ` List of things requested by lkml for reiser4 inclusion (to review) Hans Reiser
2005-09-09 17:57 ` Chris Shoemaker
2005-09-09 20:42 ` Hans Reiser
2005-09-09 20:48 ` Nish Aravamudan
2005-09-09 20:49 ` Randy.Dunlap
2005-09-09 20:57 ` Chris Shoemaker
2005-09-09 18:57 ` Christoph Hellwig
2005-09-09 19:00 ` Christoph Hellwig
2005-09-09 21:21 ` Hans Reiser
2005-09-10 4:51 ` Kyle Moffett
2005-09-10 7:28 ` Paul Jackson [this message]
2005-09-09 21:41 ` Andrew Morton
2005-09-09 22:02 ` Hans Reiser
2005-09-12 18:08 ` Hans Reiser
2005-09-12 19:40 ` Horst von Brand
2005-09-10 10:14 ` Pekka Enberg
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=20050910002851.5b984fde.pj@sgi.com \
--to=pj@sgi.com \
--cc=Reiserfs-Dev@namesys.com \
--cc=akpm@osdl.org \
--cc=edward@namesys.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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