From: Tomas Szepe <szepe@pinerecords.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Unofficial but Supported Kernel Patches
Date: Mon, 13 May 2002 01:41:09 +0200 [thread overview]
Message-ID: <20020512234109.GH1020@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0205121858570.493-100000@urtica.linuxnews.pl> <Pine.LNX.4.33L2.0205121625210.18473-100000@dragon.pdx.osdl.net>
> [Randy.Dunlap <rddunlap@osdl.org>, May-12 2002, Sun, 16:32 -0700]
> On Sun, 12 May 2002, Pawel Kot wrote:
>
> | On Sun, 12 May 2002, John Weber wrote:
> |
> | > I am trying to put a list together of all the unofficial kernel patches.
> | > I am speaking of systems like Rik's RMAP VM, and others like it.
> | >
> | > I want to put up a page on linuxhq.com with all of these patches. If
> | > you would like to have your maintained patches (or trees) listed, please
> | > shoot me an email with a description of your tree (or patch) and what is
> | > so special about it :). Also include URLs, emails, or anything else
> | > you'd like published.
> |
> | What about http://kernelnewbies.org/patches/ ?
>
> That's nice.
>
> What I would like is for someone to maintain a set of
> "required" patches to each new kernel --
> "required" here meaning "these patches are needed for kernel
> x.y.z to build or boot cleanly."
>
> The patchsets would contain only compile/link fixes and
> critical logic fixes to release and pre-release kernels.
Do you mean something even more
"select fault_and_patch from kernel group by release;" than
http://www.codemonkey.org.uk/Linux-2.5.html
?
T.
next prev parent reply other threads:[~2002-05-12 23:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 16:47 John Weber
2002-05-12 16:59 ` Pawel Kot
2002-05-12 17:23 ` John Weber
2002-05-14 20:25 ` John Levon
2002-05-12 23:32 ` Randy.Dunlap
2002-05-12 23:41 ` Tomas Szepe [this message]
2002-05-13 2:37 ` Randy.Dunlap
2002-05-13 3:01 ` John Weber
2002-05-15 13:43 ` Rob Landley
2002-05-15 20:56 ` John Levon
2002-05-16 1:44 ` Dave Jones
2002-05-13 12:32 ` Pavel Machek
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=20020512234109.GH1020@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@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 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®