Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 2 Dec 2001 16:30:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 2 Dec 2001 16:30:27 -0500 Received: from ns.suse.de ([213.95.15.193]:12554 "HELO Cantor.suse.de") by vger.kernel.org with SMTP id ; Sun, 2 Dec 2001 16:30:18 -0500 Date: Sun, 2 Dec 2001 22:30:16 +0100 (CET) From: Dave Jones To: Alan Cox Cc: Pavel Machek , Henning Schmiedehausen , Alexander Viro , Jeff Garzik , Larry McVoy , Subject: Re: Coding style - a non-issue In-Reply-To: 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 On Sun, 2 Dec 2001, Alan Cox wrote: > What would be much much more constructive isnt quite a hall of shame - its > to build a set of pages that take problem drivers and quote chunks of them > with an explanation of _why_ it is wrong, what should be used instead and > possible the "after" code if it also gets cleaned up. I planned to do something like this for the kernel-janitor project. The janitor todo-list is aparently too terse for some people, and having a perl script to point out problems wasn't enough. Maybe having the script point to a webpage explaining /why/ xxxx needs changing would be more useful. The current TODO list there goes halfway toward this, but needs expanding, more explanations etc.. Any contributions more than welcomed. regards, Dave. -- | Dave Jones. http://www.codemonkey.org.uk | SuSE Labs - 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/