From: Samuel Flory <sflory@rackable.com>
To: Brian Jackson <brian@brianandsara.net>
Cc: Orion Poplawski <orion@cora.nwra.com>, linux-kernel@vger.kernel.org
Subject: Re: Is their an explanation of various kernel versions/brances/patches/? (-mm, -ck, ..)
Date: Wed, 25 Jun 2003 16:59:44 -0700 [thread overview]
Message-ID: <3EFA3770.70806@rackable.com> (raw)
In-Reply-To: <200306251857.48341.brian@brianandsara.net>
Brian Jackson wrote:
>I don't know of a website that tracks that stuff, but here goes my knowledge
>of the different patchsets:
>
>for the most part all of them are testing grounds for patches that someday
>hope to be in the vanilla kernel
>
>mm - Andrew Morton - vm related testing ground for dev tree
>ck - Con Kolivas - desktop/interactivity patches
>kj - Kernel Janitors - testing ground for kernel cleanups on development trees
>mjb - Martin J Bligh - scalability stuff
>wli - William Lee Irwin - other vm related stuff for dev tree that Andrew
> Morton may not have time for
>ac - Alan Cox - lately it's been a testing ground for new ide
>
Actually the ac is often the test ground for new 2.4 fixes, and features.
>lsm - Chris Wright - Linux Security Modules, provides a lightweight, general
> purpose framework for access control
>osdl - Stephen Hemminger, ? maybe enterprise stuff
>laptop - Hanno Böck - unproven laptop type patches
>aa - Andrea Arcangeli - stable series vm stuff
>dj - Dave Jones - cleanups/AGP
>rmap - Rik van Riel - reverse mapping vm for 2.4
>pgcl - William Lee Irwin - ?
>
>Others? Oh yes. Maybe this is something that should be tracked on a webpage
>somewhere.
>
>--Brian Jackson
>
>On Wednesday 25 June 2003 05:02 pm, Orion Poplawski wrote:
>
>
>>Seems like everybody and their brother is maintaining a kernel patch set
>>these days :-).
>>
>>Is there a page somewhere that explains the goals of each of the various
>>versions?
>>
>>Thanks!
>>
>>- Orion
>>
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at http://www.tux.org/lkml/
>>
>>
>
>
>
--
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-06-25 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 22:02 Is their an explanation of various kernel versions/brances/patches/? (-mm, -ck, ..) Orion Poplawski
2003-06-25 23:57 ` Brian Jackson
2003-06-25 23:59 ` Samuel Flory [this message]
2003-06-26 0:02 ` William Lee Irwin III
2003-06-26 15:03 ` Disconnect
2003-06-28 10:38 ` Peter C. Ndikuwera
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=3EFA3770.70806@rackable.com \
--to=sflory@rackable.com \
--cc=brian@brianandsara.net \
--cc=linux-kernel@vger.kernel.org \
--cc=orion@cora.nwra.com \
/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;
as well as URLs for NNTP newsgroup(s).