From: Paul Jackson <pj@sgi.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: linux-kernel@vger.kernel.org, axboe@suse.de, reiser@namesys.com,
joe@perches.com, green@linuxhacker.ru, mfedyk@matchmail.com,
torvalds@osdl.org, tim@cambrant.com, markhe@nextd.demon.co.uk,
manfred@colorfullife.com, matthew@wil.cx
Subject: Re: Cleanup patches - comparison is always [true|false] + unsigned/signed compare, and similar issues. (consolidating existing threads)
Date: Thu, 8 Jan 2004 23:52:19 -0800 [thread overview]
Message-ID: <20040108235219.5d77f34b.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0401081847190.10083@jju_lnx.backbone.dif.dk>
The key question in my view was what code was easiest to understand.
This is closest to being the code that is shortest, stripped of all
non-essential detail. But not exactly. Code is more like novel or
essay in my view, than a poem. I don't find haiku clear. However,
what is easiest to understand is a judgement call.
Since we were seeing here, with the remarks of folks such as myself,
a nice example of that well known phenomenon where a committee will
debate for hours over the $25 budget line item, and then pass the
$3 million item without comment, your conclusion to try using the
Trivial Patch Monkey sounds like a winner. Rusty has good judgement,
and for changes such as this, better one good judge making immediate
decisions, than lengthy lkml threads.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
prev parent reply other threads:[~2004-01-09 7:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 17:59 Cleanup patches - comparison is always [true|false] + unsigned/signed compare, and similar issues. (consolidating existing threads) Jesper Juhl
2004-01-08 19:25 ` Tim Cambrant
2004-01-09 1:37 ` Mike Fedyk
2004-01-09 2:22 ` Jesper Juhl
2004-01-09 7:52 ` Paul Jackson [this message]
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=20040108235219.5d77f34b.pj@sgi.com \
--to=pj@sgi.com \
--cc=axboe@suse.de \
--cc=green@linuxhacker.ru \
--cc=joe@perches.com \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=markhe@nextd.demon.co.uk \
--cc=matthew@wil.cx \
--cc=mfedyk@matchmail.com \
--cc=reiser@namesys.com \
--cc=tim@cambrant.com \
--cc=torvalds@osdl.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.