From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: tim.post@netkinetics.net
Cc: linux-kernel@vger.kernel.org,
"Stefan Richter" <stefanr@s5r6.in-berlin.de>
Subject: Re: Kernel inclusion policy, meta desicion making structure?
Date: Wed, 6 Jun 2007 17:15:22 +0200 [thread overview]
Message-ID: <9a8748490706060815uefaa75bh106b30a00f63fb54@mail.gmail.com> (raw)
In-Reply-To: <4666C73F.6080208@s5r6.in-berlin.de>
On 06/06/07, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> Tim Post wrote on 2007-06-04:
> > 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.
> [...]
> > Does some document exist that shows the decision making process so that
> > I can easily answer the ultimate question of "Why not" for myself?
>
> There is documentation on how submissions should look like.
Some starting points:
Documentation/HOWTO
Documentation/SubmittingDrivers
Documentation/SubmittingPatches
Documentation/SubmitChecklist
Documentation/ManagementStyle
> Other than
> that, these are case-by-case decisions based on a number of factors.
> Perhaps you should look up discussions on merge requests (accepted as
> well as rejected ones) in archives or better at sources like LWN.net.
>
Good LKML archives to search :
http://marc.info/?l=linux-kernel
http://lkml.org/
Sometimes good summaries of discussions / decision making processes
can also be found at http://kerneltrap.org/
You can also search the ChangeLog messages for different patches
easily via git-web:
http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git;a=summary
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
prev parent reply other threads:[~2007-06-06 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 3:36 Tim Post
2007-06-06 14:39 ` Stefan Richter
2007-06-06 15:15 ` Jesper Juhl [this message]
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=9a8748490706060815uefaa75bh106b30a00f63fb54@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=tim.post@netkinetics.net \
/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®