Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 30 Jan 2002 10:48:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 30 Jan 2002 10:48:46 -0500 Received: from rudy.mif.pg.gda.pl ([153.19.42.16]:17156 "EHLO rudy.mif.pg.gda.pl") by vger.kernel.org with ESMTP id ; Wed, 30 Jan 2002 10:48:37 -0500 Date: Wed, 30 Jan 2002 16:48:14 +0100 (CET) From: =?ISO-8859-2?Q?Tomasz_K=B3oczko?= To: Ingo Molnar cc: Rob Landley , Linus Torvalds , Subject: Re: A modest proposal -- We need a patch penguin In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-2 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 29 Jan 2002, Ingo Molnar wrote: [..] > 1) cleanliness > > code cleanliness is a well-know issue, see Documentation/CodingStyle. If > a patch has such problems then maintainers are very likely to help - Linus > probably wont and shouldnt. I think place in each directory .indent.pro file with proper coding style configuration and reduce Documentation/CodingStyle to how to use indent tool can will solve many currunt problems with proper patches form and will probaly take smaller amout disk space (or aprox the same) than current Documentation/CodingStyle. Even if current indent can't handle correctly current kernel coding style IMHO it will be better inves few minutes on some changes to current indent behavior for bring this tool abilities for reindent source code in way described in Documentation/CodingStyle .. (?) kloczek -- ----------------------------------------------------------- *Ludzie nie maj? problem?w, tylko sobie sami je stwarzaj?* ----------------------------------------------------------- Tomasz K?oczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gda.pl* - 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/