From: Greg KH <greg@kroah.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Ingo Molnar <mingo@elte.hu>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: How linux-staging is released (was Re: linux-staging/linux-next merge/build errors)
Date: Sat, 21 Jun 2008 10:50:03 -0700 [thread overview]
Message-ID: <20080621175003.GC14786@kroah.com> (raw)
In-Reply-To: <1214053209.3223.220.camel@lappy.programming.kicks-ass.net>
On Sat, Jun 21, 2008 at 03:00:08PM +0200, Peter Zijlstra wrote:
>
> So what motivates people to keep working on items in your tree if
> distros are already shipping their stuff?
The fact that the code still isn't upstream?
And I'm not betting on distros picking this tree up, but it is in an
easy form if they wish to do so :)
> Will you drop drivers that stagnate?
Heh, most of the drivers are in my tree because they were stagnating
somewhere else :)
Hopefully no, it's trivial to drag them along forever, but I'll be
working to get them upstream as fast as I can, and it also provides a
very nice project for someone to pick up and work on, as a number of
developers already have.
thanks,
greg k-h
next prev parent reply other threads:[~2008-06-21 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 2:40 linux-staging/linux-next merge/build errors Stephen Rothwell
2008-06-21 7:10 ` Greg KH
2008-06-21 7:19 ` How linux-staging is released (was Re: linux-staging/linux-next merge/build errors) Greg KH
2008-06-21 13:00 ` Peter Zijlstra
2008-06-21 17:50 ` Greg KH [this message]
2008-06-21 18:02 ` Peter Zijlstra
2008-06-21 21:50 ` Greg KH
2008-06-26 12:30 ` Ingo Molnar
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=20080621175003.GC14786@kroah.com \
--to=greg@kroah.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
/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).