From: Tim Post <tim.post@netkinetics.net>
To: linux-kernel@vger.kernel.org
Subject: Kernel inclusion policy, meta desicion making structure?
Date: Mon, 04 Jun 2007 11:36:38 +0800 [thread overview]
Message-ID: <1180928198.5786.111.camel@localhost.localdomain> (raw)
Good day/evening to all.
I was wondering if a meta version of the decision making process that
would be employed to determine if a new contribution does or does not go
into the main stream Linux kernel.
The following abstract demonstrates my question if it does not make
sense:
"There are many file systems made for the Linux kernel. Only some of
them are present by default in released Kernels."
"There is an AoE block module in the Kernel, but not the userspace blade
module. Only one was included."
Does some document exist that shows the decision making process so that
I can easily answer the ultimate question of "Why not" for myself? It
would be fun to examine code until I could answer the question myself,
and very educational for me as a programmer. Once I figure it out, I
"own" just a little more knowledge without pestering you guys.
I would like to write my own lightweight cluster file system and make
modifications to existing cluster file systems. I think first I should
better learn in practice whats wrong with existing before I go improving
it :) This document would be the best starting point for me.
Thank you in advance for any links. My question is obscure and thus hard
to search for in the archives, I post only after doing so.
Best regards,
--Tim
next reply other threads:[~2007-06-04 4:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 3:36 Tim Post [this message]
2007-06-06 14:39 ` Stefan Richter
2007-06-06 15:15 ` Jesper Juhl
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=1180928198.5786.111.camel@localhost.localdomain \
--to=tim.post@netkinetics.net \
--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®