From: James Smart <James.Smart@Emulex.Com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Joe Perches <joe@perches.com>, Greg KH <gregkh@suse.de>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
James Bottomley <James.Bottomley@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Theodore Tso <tytso@mit.edu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jing Huang <huangj@brocade.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Moving drivers into staging (was Re: [GIT PULL] SCSI fixes for 2.6.32-rc3)
Date: Wed, 14 Oct 2009 10:13:59 -0400 [thread overview]
Message-ID: <4AD5DCA7.5060704@emulex.com> (raw)
In-Reply-To: <20091014063308.GE784@elte.hu>
Ingo Molnar wrote:
> Yes, that's a real worry. Some time ago i suggested:
>
> drivers/staging/good/
> drivers/staging/bad/
> drivers/staging/ugly/
>
> good: drivers that are to go upstream in the next cycle
> bad: outgoing drivers being obsoleted or abandoned
> ugly: incoming messy drivers with active developers
>
> The messaging of this looks nice and the names are short and obvious.
>
> An added benefit is that this kind of separation makes it easy for
> people interested in drivers/staging to follow the 'status' of drivers.
> Once stuff goes into 'good' a different kind of review is needed than if
> a driver goes into 'ugly'.
>
> The main disadvantage would be the PR angle: putting new drivers into a
> path named 'ugly'. Not something you want to put into a quarterly status
> report, right? If we put drivers/staging/ugly/ drivers into
> drivers/staging/ itself, we'd solve that problem. I.e. we'd keep the
> current scheme, but we'd also add drivers/staging/good/ and
> drivers/staging/bad/ as two extra stages for incoming and outgoing
> drivers.
Change "ugly" to "wip" (work in progress). Should remove the negative
connotation and keeps things short. Does miss the spaghetti western theme
though :)
-- james s
next prev parent reply other threads:[~2009-10-14 14:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1255031298.4187.260.camel@mulgrave.site>
[not found] ` <alpine.LFD.2.01.0910081252090.3432@localhost.localdomain>
[not found] ` <alpine.LFD.2.01.0910081255510.3432@localhost.localdomain>
[not found] ` <20091008210737.GD29181@mit.edu>
[not found] ` <alpine.LFD.2.01.0910081410400.3432@localhost.localdomain>
[not found] ` <20091009091538.GA4154@elte.hu>
[not found] ` <1255097287.2934.21.camel@localhost.localdomain>
[not found] ` <20091012130652.GB25464@elte.hu>
[not found] ` <1255357148.2850.91.camel@localhost.localdomain>
[not found] ` <20091012145453.GD4565@elte.hu>
2009-10-12 15:09 ` Moving drivers into staging (was Re: [GIT PULL] SCSI fixes for 2.6.32-rc3) Greg KH
2009-10-12 15:42 ` Ingo Molnar
[not found] ` <20091012154244.GA13323-X9Un+BFzKDI@public.gmane.org>
2009-10-12 23:24 ` Greg KH
2009-10-13 18:08 ` Luis R. Rodriguez
2009-10-14 4:45 ` Greg KH
[not found] ` <20091014044519.GA19199-l3A5Bk7waGM@public.gmane.org>
2009-10-14 5:19 ` Joe Perches
2009-10-14 6:33 ` Ingo Molnar
2009-10-14 14:13 ` James Smart [this message]
2009-10-14 17:52 ` Stefan Richter
2009-10-14 18:36 ` Ingo Molnar
2009-10-14 19:00 ` Stefan Richter
2009-10-15 6:03 ` Ingo Molnar
2009-10-14 19:11 ` Greg KH
[not found] ` <20091012150911.GB1656-l3A5Bk7waGM@public.gmane.org>
2009-10-12 15:43 ` James Bottomley
2009-10-12 23:26 ` Greg KH
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=4AD5DCA7.5060704@emulex.com \
--to=james.smart@emulex.com \
--cc=James.Bottomley@suse.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=huangj@brocade.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).