From: Hans Reiser <reiser@namesys.com>
To: Steven Cole <elenstev@mesatop.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>, Val Henson <val@nmt.edu>,
Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Those ruddy punctuation fixes
Date: Fri, 07 Mar 2003 20:04:22 +0300 [thread overview]
Message-ID: <3E68D116.6040304@namesys.com> (raw)
In-Reply-To: <1047009782.4114.108.camel@spc1.mesatop.com>
You are fixing things and people are giving you shit for it. People who
want evidence that making something better is worth doing before they do
it are.... Sigh. In the unlikely event that Linus doesn't take your
fixes directly, I'll take them for reiserfs, just let me know. ReiserFS
code is as good as we know how to make it, as a matter of policy, and
that includes the comments.
--
Hans
next prev parent reply other threads:[~2003-03-07 16:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 11:10 Those ruddy punctuation fixes Russell King
2003-03-05 11:22 ` John Bradford
2003-03-05 14:18 ` Mike Dresser
2003-03-06 1:50 ` jw schultz
2003-03-06 9:58 ` Russell King
2003-03-06 10:46 ` John Bradford
2003-03-05 12:20 ` Dave Jones
2003-03-05 11:37 ` good info on memory management Prasad Kamath
2003-03-05 12:03 ` Terje Eggestad
2003-03-06 8:16 ` Ranjeet Shetye
2003-03-06 3:11 ` Those ruddy punctuation fixes Steven Cole
2003-03-07 1:04 ` Val Henson
2003-03-07 2:44 ` Steven Cole
2003-03-07 3:33 ` Martin J. Bligh
2003-03-07 4:02 ` Steven Cole
2003-03-07 5:11 ` Martin J. Bligh
2003-03-07 17:04 ` Hans Reiser [this message]
[not found] ` <mailman.1047000901.5238.linux-kernel2news@redhat.com>
2003-03-07 3:07 ` Pete Zaitcev
2003-03-07 7:16 Dan Kegel
2003-03-07 17:17 ` Benjamin LaHaise
2003-03-07 18:00 ` Dan Kegel
2003-03-07 23:15 ` Alan Cox
2003-03-08 0:52 ` Dave Jones
2003-03-08 0:04 ` Randy.Dunlap
2003-03-08 0:29 ` Werner Almesberger
2003-03-08 1:09 ` Dan Kegel
2003-03-08 2:18 ` Werner Almesberger
2003-03-08 1:08 ` 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=3E68D116.6040304@namesys.com \
--to=reiser@namesys.com \
--cc=davej@codemonkey.org.uk \
--cc=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=val@nmt.edu \
/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;
as well as URLs for NNTP newsgroup(s).