From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DMARC_NONE,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from member.michigannet.com (member.michigannet.com [207.158.188.18]) by chiba.3jane.net (Postfix) with ESMTP id 88030ABCFC for ; Fri, 10 May 2002 23:26:21 -0500 (CDT) Received: from squish.home.loc (annex-0-3-port3.dialup.coast.net [207.158.191.3]) by member.michigannet.com (8.11.6/8.11.0) with ESMTP id g4B4RPt28901 for ; Sat, 11 May 2002 00:27:26 -0400 Received: by squish.home.loc (Postfix, from userid 666) id DA40827AFF; Sat, 11 May 2002 00:26:17 -0400 (EDT) Date: Sat, 11 May 2002 00:26:17 -0400 From: Paul To: gentoo-dev@gentoo.org Message-ID: <20020511002617.J27749@squish.home.loc> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from spkane@genomatica.com on Thu, May 09, 2002 at 10:50:14PM -0700 Subject: [gentoo-dev] Re: patching the kernel Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 0fb0548c-b654-425a-8317-5f6e58b67d32 X-Archives-Hash: 773c98c30cea4a81f6bb2a59a79a03d1 "Sean P. Kane" , on Thu May 09, 2002 [10:50:14 PM] said: > I've been looking at the gentoo-sources ebuild and noticed that it seems to have the kernel tarball and then simply one big patch for the rest. I was hoping to be able to update one of the patches for some testing I wanted to do. Is there any reason that we don't keep the patches seperate to make this sort of work easier? Or am I missing a simple solution to this? > > Thanks, > Sean > Hi; At least the last two -r? gentoo-sources ebuilds have had URLs to all the included patch sets. (this is a huge improvement) Im sure agglomerating them into one big patchset is merely a matter of convenience. Keeping them separate would make it a lot easier to engage in the kind of experimentation you are talking about by editing the ebuild... Until/if that ever happens, you can download the patch in question, as specified in the ebuild comment, and use patch -R to remove it, then modify/replace it with another patch... Paul set@pobox.com