From: Shawn <core@enodev.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@digeo.com>, mingo@elte.hu
Subject: [REPORT] 2.5.65-mm1
Date: 19 Mar 2003 03:58:44 -0600 [thread overview]
Message-ID: <1048067924.21567.7.camel@localhost.localdomain> (raw)
Well, 2.5.65-mm1 trashed all my data... Just kidding.
Actually, I'm sitting here with a load of over 25, and my gnome2 menus
go like they're being chased by friggin fire ants. How many cans of
whoop-ass does linux have to open for crying out loud???
Almost like anticipatory /menus/! ;) Almost think I hear a *whoosh* as
I'm plinking around with 20 cpp processes running simultaneously. Nice!
Damn nice!
So, I guess this is a subjective interactivity changes report. So, now,
Performance == Holy sheet!
next reply other threads:[~2003-03-19 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 9:58 Shawn [this message]
2003-03-19 19:48 ` Josh McKinney
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=1048067924.21567.7.camel@localhost.localdomain \
--to=core@enodev.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®