Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266812AbUFRUTl (ORCPT ); Fri, 18 Jun 2004 16:19:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266811AbUFRUJT (ORCPT ); Fri, 18 Jun 2004 16:09:19 -0400 Received: from mx1.redhat.com ([66.187.233.31]:64184 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S266799AbUFRUF5 (ORCPT ); Fri, 18 Jun 2004 16:05:57 -0400 Date: Fri, 18 Jun 2004 16:05:46 -0400 (EDT) From: Rik van Riel X-X-Sender: riel@chimarrao.boston.redhat.com To: Tim Bird cc: Jan-Benedict Glaw , , William Lee Irwin III , Jens Axboe , Andrew Morton , 4Front Technologies Subject: Re: Stop the Linux kernel madness In-Reply-To: <40D33C58.1030905@am.sony.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1044 Lines: 24 On Fri, 18 Jun 2004, Tim Bird wrote: > Jan-Benedict Glaw wrote: > The idea of having some dedicated developers perform this function is > actually a pretty good one, although I wouldn't burden Linus with > managing them. That is, it might be useful to have some people > following behind embedded product developers trying to glean, > generalize, forward-port and otherwise clean-up patches that would > otherwise never see the light of day. Since the people benefitting from this work are the embedded developers, it would seem logical that they should bear the cost of this effort, too. -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan - 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/