From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S262117AbVGVRMP@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S262117AbVGVRMP (ORCPT <rfc822;willy@w.ods.org>);
	Fri, 22 Jul 2005 13:12:15 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262119AbVGVRMP
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Fri, 22 Jul 2005 13:12:15 -0400
Received: from wproxy.gmail.com ([64.233.184.199]:22993 "EHLO wproxy.gmail.com")
	by vger.kernel.org with ESMTP id S262117AbVGVRMN convert rfc822-to-8bit
	(ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Fri, 22 Jul 2005 13:12:13 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=C163GYZI/wzb2SxfVHij8DxMGJe3idMTyCRbm/HYeQbym4E5pK5UUEMlx242JthojYrUjvR5mE4uDohJBmAx9jOaZeVVBAu5MsiqkEtxajQHNKCDYj0293Lwk97s0jdLFECHenz7VetKam0qgTZ+kXoLvuj5URwENE+gObND6U4=
Message-ID: <6981e08b050722101241ba2f3e@mail.gmail.com>
Date: Fri, 22 Jul 2005 12:12:12 -0500
From: Patrick Draper <pdraper@gmail.com>
Reply-To: Patrick Draper <pdraper@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel guide to space
In-Reply-To: <m3pstd2jfu.fsf@defiant.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
References: <20050711145616.GA22936@mellanox.co.il>
	 <9a87484905072005596f2c2b51@mail.gmail.com>
	 <m3pstd2jfu.fsf@defiant.localdomain>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Why isn't a code formatting program used? People could write the code
as they like to write it, then format it automatically in a standard
way before it gets put into the kernel.

Patrick