From: Nick Piggin <nickpiggin@yahoo.com.au>
To: ncunningham@linuxmail.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Proposal: Desktop kernel bk tree/patchset.
Date: Thu, 21 Oct 2004 19:26:35 +1000 [thread overview]
Message-ID: <417780CB.4060106@yahoo.com.au> (raw)
In-Reply-To: <1098344977.4146.21.camel@desktop.cunninghams>
Nigel Cunningham wrote:
> Hi all.
>
> I want to get some feedback. I'm considering making a tree/patchset
> aimed at the desktop user: Linus kernel + PM, USB and so on patches,
> Win4Lin patches and perhaps [I/O] scheduler improvements.
>
> What do people think?
>
I don't think it would be a really good idea to have an official tree
for desktop users. A staging area for desktop improvements, sure that
would be no problem. But if you really have some good improvements,
they should eventually get into the mainline kernel where you can
expect a pretty good (or not terribly bad) review and testing process.
On the other hand, I understand you're probably frustrated at the slow
pace and politics of getting more ambitious patches into the kernel.
I'd go for angle of aiming to get things into -mm. Andrew generally
doesn't mind brewing things up there, even if there is no clear path
for merging into 2.6 at the time... so long as they're pretty stable
and not going to cause rejects all over the tree, of course.
Just my two cents.
next prev parent reply other threads:[~2004-10-21 9:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 7:49 Proposal: Desktop kernel bk tree/patchset Nigel Cunningham
2004-10-21 8:16 ` Felipe Alfaro Solana
2004-10-21 8:36 ` Dumitru Ciobarcianu
2004-10-21 9:00 ` Alan Cox
2004-10-21 9:26 ` Nick Piggin [this message]
2004-10-21 21:21 ` Nigel Cunningham
2004-10-21 13:34 ` Diego Calleja
2004-10-21 16:17 ` Greg KH
2004-10-21 21:23 ` Nigel Cunningham
2004-10-21 21:41 ` Greg KH
2004-10-21 21:51 ` Nigel Cunningham
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=417780CB.4060106@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.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