From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jozsef Kadlecsik Subject: Re: Call for testing: patch-o-matic-ng Date: Mon, 5 Jan 2004 12:32:35 +0100 (CET) Sender: netfilter-devel-admin@lists.netfilter.org Message-ID: References: <20040101163627.GD3530@obroa-skai.de.gnumonks.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Netfilter Development Mailinglist Return-path: To: Harald Welte In-Reply-To: <20040101163627.GD3530@obroa-skai.de.gnumonks.org> Errors-To: netfilter-devel-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Id: netfilter-devel.vger.kernel.org On Thu, 1 Jan 2004, Harald Welte wrote: > a 2.6 specific patch would then be inside a linux-2.6 directory. The > only remaining question is: > > - how to encode the information 'which patch for which version' in the > info file ? We would need something like > "if linux >= 2.6.0 && linux < 2.7.0, then use linux-2.6 and > linux-2.6.patch" > > - what about patchlets that have the same wholefiles but a different > 'patch' file. I.e. a new conntrack helper that has the same source > file, valid for 2.4 and 2.6 - but a different diff for patching > something into conntrack_core ? Something like 'best match wins'? linux-2.6.13 - just for 2.6.13 linux-2.6 - every (other) 2.6 release linux-2.4 - every 2.4 release linux - every other release :-) (Same goes for the linux.patch file.) 'Requires' could be used to set general version bounds, like Requires: linux >= 2.4.22 Best regards, Jozsef - E-mail : kadlec@blackhole.kfki.hu, kadlec@sunserv.kfki.hu PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt Address : KFKI Research Institute for Particle and Nuclear Physics H-1525 Budapest 114, POB. 49, Hungary