From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 13:38:25 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 19C073F9 for ; Wed, 10 Jul 2013 13:38:25 +0000 (UTC) (envelope-from thierry@pompo.net) Received: from mx1a.lautre.net (eyra.lautre.net [80.67.160.71]) by mx1.freebsd.org (Postfix) with ESMTP id D67A61DD7 for ; Wed, 10 Jul 2013 13:38:24 +0000 (UTC) Received: from graf.pompo.net (graf.pompo.net [78.225.128.39]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: thierry@pompo.net) by mx1a.lautre.net (Postfix) with ESMTPSA id 44D5240A5B for ; Wed, 10 Jul 2013 15:38:18 +0200 (CEST) Received: by graf.pompo.net (Postfix, from userid 1001) id A833142D28ED; Wed, 10 Jul 2013 15:38:17 +0200 (CEST) Date: Wed, 10 Jul 2013 15:38:17 +0200 From: Thierry Thomas To: freebsd-fortran@freebsd.org Subject: Re: why fortran mailing list? Message-ID: <20130710133817.GB41178@graf.pompo.net> Mail-Followup-To: freebsd-fortran@freebsd.org References: <20130710084713.GA73590@graf.pompo.net> <201307100908.r6A98jOM001342@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201307100908.r6A98jOM001342@mech-cluster241.men.bris.ac.uk> X-Operating-System: FreeBSD 9.1-STABLE i386 Organization: Kabbale Eros X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc; y=\ipKMNm<1J>lv@PP~7Z<.t KjAnXLs: X-PGP: 0xC71405A2 User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 13:38:25 -0000 Le mer 10 jul 13 à 11:08:45 +0200, Anton Shterenlikht écrivait : > Regarding this patch, is it ok to just put it > unde files, as: > > # ls files/ > medis-patch-Lib_Makefile.txt patch-Lib::proto.h patch-Test::Makefile > patch-CONFIG::configure patch-Lib_Makefile patch-onmetis > patch-CONFIG_onmetis.in patch-Programs::Makefile > # > > How does the ports framework know that > medis-patch-Lib_Makefile.txt must be applied > *after* patch-Lib_Makefile, i.e. on top of it? Actually, it has to be renamed as patch-*. And patches are applied sorted by their name. > P.S. Please ignore my reply to ports/176328. > I understand now what to do. Great! -- Th. Thomas.