From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: linux-kernel@vger.kernel.org
Subject: RFC: The Big Patch List (was: Linux Kernel-2.4.18-nj1)
Date: Sat, 5 Jan 2002 22:06:14 +0100 [thread overview]
Message-ID: <20020105210614.GA19599@emma1.emma.line.org> (raw)
In-Reply-To: <20020105180601.GC756@cpe-24-221-152-185.az.sprintbbd.net> <20020105194140.67038.qmail@web20504.mail.yahoo.com>
In-Reply-To: <20020105194140.67038.qmail@web20504.mail.yahoo.com>
On Sat, 05 Jan 2002, willy tarreau wrote:
> Perhaps people who have a solid personal tree would
> like to continue this discussion off-list and find
> an arrangement about a single test tree. Concerning
> stable trees, I think that both Marcello's and
> Andrea's are rock solid. Othe people may want to use
> their distributor's.
What *I* personally would greatly appreciate: the Big List of Kernel
Patches. It would list a patch, what it does, what version of the kernel
it is against, where it can be found, and maybe where other versions can
be found or conflicts.
This list could e. g. look like (cast into any form you like, an
extensible one is a good idea); I've just picked a random patch that I
use, without any recommendation:
PATCH: Pre-Emptive Kernel
AUTHOR: Robert M. Love
SUMMARY: Makes most parts of the kernel preemptive to reduce latency.
URL: http://www.tech9.net/rml/linux/
PATCHES-STABLE: 2.4.16, 2.4.17 <- only list patches yielding working releases
PATCHES-STABLE-PRE: 2.4.18-pre1
PATCHES-DEVEL: 2.5.1
PATCHES-DEVEL-PRE: 2.5.2-pre1
REQUISITES: -
CONFLICTS: O(1) scheduler
Resembles MAINTAINERS? Rightly so, just more detail given.
That way, we would not need to have so many distinct trees, but this
could easily grow into a patch repository where people could pull their
patches from. I presume that conflicts between patches meant for
inclusion will be worked out; maybe this list should announce
sub-versions of the patches, like Willy mentioned:
PATCH: ReiserFS for ext3-enabled kernels
AUTHOR: Hans Reiser et al.; Matthias Andree et al. (ext3 compatibility)
URL: http://mandree.home.pages.de/kernelpatches/v2.2/v2.2.19/
PATCHES-STABLE: 2.2.19
PATCHES-STABLE-PRE: -
PATCHES-DEVEL: -
PATCHES-DEVEL-PRE: -
REQUISITES: -
CONFLICTS: -
You get the idea. Comments?
--
Matthias Andree
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." Benjamin Franklin
next prev parent reply other threads:[~2002-01-05 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 10:52 Linux Kernel-2.4.18-nj1 Willy Tarreau
2002-01-05 18:06 ` Tom Rini
2002-01-05 19:41 ` willy tarreau
2002-01-05 21:06 ` Matthias Andree [this message]
2002-01-05 22:13 ` RFC: The Big Patch List (was: Linux Kernel-2.4.18-nj1) John Levon
2002-01-05 21:42 ` Linux Kernel-2.4.18-nj1 Tom Rini
2002-01-06 1:33 ` The plethora of kernel versions brian
2002-01-06 8:53 ` willy tarreau
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=20020105210614.GA19599@emma1.emma.line.org \
--to=matthias.andree@stud.uni-dortmund.de \
--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
all inboxes | Powered by JetHome®