Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 20 Jul 2002 20:13:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 20 Jul 2002 20:13:33 -0400 Received: from garrincha.netbank.com.br ([200.203.199.88]:29960 "HELO garrincha.netbank.com.br") by vger.kernel.org with SMTP id ; Sat, 20 Jul 2002 20:13:32 -0400 Date: Sat, 20 Jul 2002 21:12:00 -0300 (BRT) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: Linus Torvalds cc: Alan Cox , Robert Love , Andrew Morton , Subject: Re: [PATCH] VM strict overcommit In-Reply-To: Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org 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: 1155 Lines: 31 On Sat, 20 Jul 2002, Linus Torvalds wrote: > Good. I hate the fact that so many people seem to think that adding 15 > lines of copyright notice to a file somehow makes it "more legal". All it > does is to give some corporate lawyer a bone, and take up precious > real-estate on the first thing you see when you open the file that could > be used to actually say what the file does (and who has worked on it). On a related note, it would be nice if files had a one- (or two-)line description near the top saying what the code in this file is supposed to do. That should cut down on the time people spend searching the kernel for code and maybe even reduce code duplication... Would a series of small documentation patches adding small descriptions to the top of files be welcome ? regards, Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://distro.conectiva.com/ - 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/