Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755464AbZJNGeB (ORCPT ); Wed, 14 Oct 2009 02:34:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754582AbZJNGeA (ORCPT ); Wed, 14 Oct 2009 02:34:00 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:42343 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751220AbZJNGd7 (ORCPT ); Wed, 14 Oct 2009 02:33:59 -0400 Date: Wed, 14 Oct 2009 08:33:08 +0200 From: Ingo Molnar To: Joe Perches Cc: Greg KH , "Luis R. Rodriguez" , James Bottomley , Linus Torvalds , Theodore Tso , Andrew Morton , linux-scsi , linux-kernel , Jing Huang , netdev@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) Message-ID: <20091014063308.GE784@elte.hu> References: <1255097287.2934.21.camel@localhost.localdomain> <20091012130652.GB25464@elte.hu> <1255357148.2850.91.camel@localhost.localdomain> <20091012145453.GD4565@elte.hu> <20091012150911.GB1656@suse.de> <20091012154244.GA13323@elte.hu> <20091012232429.GA24254@suse.de> <43e72e890910131108m789110b4hc35e25601ad67bb7@mail.gmail.com> <20091014044519.GA19199@suse.de> <1255497575.1851.16.camel@Joe-Laptop.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1255497575.1851.16.camel@Joe-Laptop.home> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1839 Lines: 49 * Joe Perches wrote: > On Tue, 2009-10-13 at 21:45 -0700, Greg KH wrote: > > How about when it was scheduled to be removed, we put it in staging and > > I'll add it to my announcements about the staging tree every release? > > Unless you can think of a better way? > > staging/to_be_removed_unless_fixed_by/v.x.y ? 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. A third version would be a more neutral name: drivers/staging/incoming/ drivers/staging/outgoing/ I think it has many advantages, but (of course!) it all depends on whether Greg wants to have any separation like this. Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/