From: Bas Mevissen <ml@basmevissen.nl>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.22-rc2-ac3
Date: Mon, 18 Aug 2003 11:53:06 +0200 [thread overview]
Message-ID: <3F40A202.60701@basmevissen.nl> (raw)
In-Reply-To: <200308162139.h7GLdW415121@devserv.devel.redhat.com>
Alan Cox wrote:
> Linux 2.4.22-rc2-ac3
Cool. But a few questions:
1) Can you supply (automatically created) incremental patches? It saves
a lot of time to just be able to apply the increments in a (manually)
patched up tree. Furthermore, it saves download time as it is a huge
patch (POTS modem...).
2) What about the new scheduler? Is that a candidate for 2.4.23 (or even
2.4.22)? I'm asking this because I'm playing around with swsusp patches
(created for 2.4.21) and the new scheduler in -ac breaks a few things
there. If is is a candidate for 2.4.xx real soon, then we need to fix
it. Otherwise, it can be postponed.
Regards,
Bas.
next prev parent reply other threads:[~2003-08-18 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 21:39 Linux 2.4.22-rc2-ac3 Alan Cox
2003-08-18 3:07 ` Gerardo Exequiel Pozzi
2003-08-18 9:53 ` Bas Mevissen [this message]
2003-08-18 12:22 ` 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=3F40A202.60701@basmevissen.nl \
--to=ml@basmevissen.nl \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.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