From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269097AbUHXW5R (ORCPT ); Tue, 24 Aug 2004 18:57:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269096AbUHXW5Q (ORCPT ); Tue, 24 Aug 2004 18:57:16 -0400 Received: from e35.co.us.ibm.com ([32.97.110.133]:12714 "EHLO e35.co.us.ibm.com") by vger.kernel.org with ESMTP id S269097AbUHXWzn (ORCPT ); Tue, 24 Aug 2004 18:55:43 -0400 Subject: Re: Linux 2.6.9-rc1 From: Dave Hansen To: "Martin J. Bligh" Cc: Linus Torvalds , Matt Mackall , Kernel Mailing List In-Reply-To: <64420000.1093382553@[10.10.2.4]> References: <20040824184245.GE5414@waste.org> <64420000.1093382553@[10.10.2.4]> Content-Type: text/plain Message-Id: <1093388119.4030.116.camel@nighthawk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 24 Aug 2004 15:55:19 -0700 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2004-08-24 at 14:22, Martin J. Bligh wrote: > >From an automated tool point of view, it's easier to build a kernel > with just tarball + 1 patch (I have much the same issues as Matt to deal > with) ... also it works the same way as the current -rc releases, etc, > so it's consistent. The post-releases have tarballs all by themselves, though. So, you shouldn't really have anything to worry about for any of the post releases, unless you're using something like ketchup which skips the tarballs in favor of patching. -- Dave