From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261426AbUHaQRl (ORCPT ); Tue, 31 Aug 2004 12:17:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261711AbUHaQRk (ORCPT ); Tue, 31 Aug 2004 12:17:40 -0400 Received: from users.linvision.com ([62.58.92.114]:28889 "HELO bitwizard.nl") by vger.kernel.org with SMTP id S261474AbUHaQR3 (ORCPT ); Tue, 31 Aug 2004 12:17:29 -0400 Date: Tue, 31 Aug 2004 18:17:28 +0200 From: Erik Mouw To: Jeff Garzik Cc: Linux Kernel , Andrew Morton , Jeremy Higdon Subject: Re: [DOC] Linux kernel patch submission format Message-ID: <20040831161728.GE17261@harddisk-recovery.com> References: <413431F5.9000704@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <413431F5.9000704@pobox.com> User-Agent: Mutt/1.3.28i Organization: Harddisk-recovery.com Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 31, 2004 at 04:08:21AM -0400, Jeff Garzik wrote: > I tried to keep it as short as possible: here is a page describing the > most optimal format for sending patches to Linux kernel developers. > > http://linux.yyz.us/patch-format.html Looks good. > This URL should be permanent, feel free to bookmark it. > Comments welcome. What about including this in the kernel tarball itself so it can't get lost? You could include it in Documentation/SubmittingPatches. Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands