From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from srv5.dvmed.net ([207.36.208.214]:51311 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763836AbYBLSCq (ORCPT ); Tue, 12 Feb 2008 13:02:46 -0500 Message-ID: <47B1DF42.2090808@garzik.org> Date: Tue, 12 Feb 2008 13:02:42 -0500 From: Jeff Garzik MIME-Version: 1.0 Subject: Re: Announce: Linux-next (Or Andrew's dream :-)) References: <20080212120208.f7168a91.sfr@canb.auug.org.au> In-Reply-To: <20080212120208.f7168a91.sfr@canb.auug.org.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: LKML , linux-next@vger.kernel.org, linux-arch@vger.kernel.org, Andrew Morton , Linus Stephen Rothwell wrote: > Andrew was looking for someone to run a linux-next tree that just > contained the subsystem git and quilt trees for 2.6.x+1 and I (in a > moment of madness) volunteered. So, this is to announce the creating of > such a tree (it doesn't exist yet) which will require some (hopefully) > small amount of work on the part of subsystem maintainers. As noted to Andrew in private email, I think this would be great. akpm's -mm tree tends to have "x+1" changes in it, and also stuff that's not fully baked yet. I would definitely like to see a tree composed of all the sub-trees where maintainers said "yes, I think this is baked and ready for x+1". Then -mm and not-yet-baked git changes can layer on top of that. As others are noting, API changes require some coordination amongst ourselves (should be our job, not yours, really) and historically we haven't been so good at that -- in part because IMO there hasn't been any system thing better than a heads-up email in place. Jeff