From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Joakim Tjernlund <Joakim.Tjernlund@lumentis.se>
Cc: Paul Mackerras <paulus@samba.org>,
"Linuxppc-Dev@Lists. Linuxppc. Org"
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: memmove broken
Date: Mon, 7 Jul 2003 14:06:06 +0200 [thread overview]
Message-ID: <20030707120606.GC7104@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <003301c34473$0f88d7a0$020120b0@jockeXP>
On Mon, 7 July 2003 12:32:21 +0200, Joakim Tjernlund wrote:
>
> > Agreed. And even then, I don't want to submit it before 2.7.
>
> Why? Just look at 2.4 and you will find much boulder stuff going
> in there than this.
Other people's bad example is no justification for my misbehaviour. ;)
This patch doesn't fix anything that is wrong, and it doesn't add
functionality that isn't there right now. Performance is the least
important aspect of computing, unless it has an impact on
functionality as well. (audio without glitches and such)
Besides, Marcelo didn't even take my fixes for the zlib yet, so there
is more important stuff in the queue.
Jörn
--
Fancy algorithms are slow when n is small, and n is usually small.
Fancy algorithms have big constants. Until you know that n is
frequently going to be big, don't get fancy.
-- Rob Pike
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-07 12:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 17:20 memmove broken Joakim Tjernlund
2003-07-04 6:17 ` Paul Mackerras
2003-07-04 8:32 ` Joakim Tjernlund
2003-07-04 9:37 ` Paul Mackerras
2003-07-04 11:07 ` Joakim Tjernlund
2003-07-04 23:38 ` Paul Mackerras
2003-07-05 7:21 ` Jörn Engel
2003-07-05 9:55 ` Holger Bettag
2003-07-05 13:01 ` Paul Mackerras
2003-07-05 14:57 ` Joakim Tjernlund
2003-07-05 17:01 ` Jörn Engel
2003-07-07 10:32 ` Joakim Tjernlund
2003-07-07 12:06 ` Jörn Engel [this message]
2003-07-07 12:58 ` Joakim Tjernlund
2003-07-07 13:16 ` Jörn Engel
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=20030707120606.GC7104@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=Joakim.Tjernlund@lumentis.se \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).