From owner-freebsd-ports@FreeBSD.ORG Sat Jun 9 19:16:12 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E019D106566C for ; Sat, 9 Jun 2012 19:16:12 +0000 (UTC) (envelope-from rflynn@acsalaska.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id AD10C8FC0C for ; Sat, 9 Jun 2012 19:16:12 +0000 (UTC) Received: from [127.0.0.1] (squeeze.lan.rachie.is-a-geek.net [192.168.2.30]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id D2FEA7E887; Sat, 9 Jun 2012 11:16:10 -0800 (AKDT) Message-ID: <4FD3A0F4.50802@acsalaska.net> Date: Sat, 09 Jun 2012 21:16:04 +0200 From: Mel Flynn User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Matthew Seaman References: <20120608204143.5a1d780a@dijkstra.cruwe.de> <4FD268B5.4050103@infracaninophile.co.uk> <20120609132520.42b0af28@dijkstra.cruwe.de> <4FD33B6A.7050206@infracaninophile.co.uk> In-Reply-To: <4FD33B6A.7050206@infracaninophile.co.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org, "Christopher J. Ruwe" Subject: Re: math/ess CONFLICTS with devel/noweb, help with CONFLICTS= needed X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2012 19:16:13 -0000 On 9-6-2012 14:02, Matthew Seaman wrote: > On 09/06/2012 12:25, Christopher J. Ruwe wrote: >> Thanks for your quick answer. Incidentally, I am at this moment also >> preparing a maintainer update for a new version of math/ess. Should I >> perpare two PRs, one for the CONFLICTS and one for the actual update or >> is it permissable to pack these two into one? > > It is best to put all the changes you want to make into one PR. That > will get it processed most efficiently. And if there's a PR for the conflict problem, then mention in your update PR that this update "closes PR xxxxxx". -- Mel