From: Mike Fedyk <firstname.lastname@example.org>
To: Eugene Teo <email@example.com>
Cc: Con Kolivas <firstname.lastname@example.org>,
linux kernel mailing list <email@example.com>,
Andrew Morton <firstname.lastname@example.org>, Mike Galbraith <email@example.com>,
Davide Libenzi <firstname.lastname@example.org>
Subject: Re: [PATCH] O7int for interactivity
Date: Sat, 19 Jul 2003 09:23:04 -0700 [thread overview]
Message-ID: <20030719162304.GA1059@matchmail.com> (raw)
On Sat, Jul 19, 2003 at 11:40:59AM +0800, Eugene Teo wrote:
> <quote sender="Mike Fedyk">
> > On Sat, Jul 19, 2003 at 02:10:49AM +1000, Con Kolivas wrote:
> > > Here is an update to my Oint patches for 2.5/6 interactivity. Note I will be
> > > away for a week so bash away and abuse this one lots and when I get back I can
> > > see what else needs doing. Note I posted a preview earlier but this is the formal
> > > O7 patch (check the datestamp which people hate in the naming of my patches).
> > > I know this is turning into a marathon effort but... as you're all probably aware
> > > there is nothing simple about tuning this beast. Thanks to all the testers and
> > > people commenting; keep it coming please.
> > Is this on top of 06 or 06.1?
> His patches are usually on top of the previous patch,
> so if you applied O6int, apply O6.1int on it, then O7int on O6.1int.
> But do read his readme file when you download it.
Yeah, I didn't even go to his web site. I've been taking his patches sent
through email, saving it to a file, and running that through patch... :-D
next prev parent reply other threads:[~2003-07-19 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 16:10 [PATCH] O7int for interactivity Con Kolivas
2003-07-18 22:53 ` Felipe Alfaro Solana
2003-07-19 3:39 ` Eugene Teo
2003-07-18 23:07 ` Mike Fedyk
2003-07-18 23:30 ` Con Kolivas
2003-07-18 23:41 ` Mike Fedyk
2003-07-21 17:23 ` Mike Fedyk
2003-07-19 3:40 ` Eugene Teo
2003-07-19 16:23 ` Mike Fedyk [this message]
2003-07-19 1:08 ` William Lee Irwin III
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.