From owner-freebsd-ports@FreeBSD.ORG Tue Apr 1 00:45:11 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2F45FFA6; Tue, 1 Apr 2014 00:45:11 +0000 (UTC) Received: from mail.feld.me (mail.feld.me [66.170.3.6]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.feld.me", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B81ACB15; Tue, 1 Apr 2014 00:45:10 +0000 (UTC) Received: from mail.feld.me (mail.feld.me [66.170.3.6]); by mail.feld.me (OpenSMTPD) with ESMTP id ecc7f8d7; Mon, 31 Mar 2014 19:45:01 -0500 (CDT) Received: from feld@feld.me by mail.feld.me (Archiveopteryx 3.2.0) with esmtpsa id 1396313099-80816-3394/5/63; Tue, 1 Apr 2014 00:44:59 +0000 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Subject: Re: ports/182985 maintainer timeout From: Mark Felder In-Reply-To: <5334D5AD.8030800@laskoprinting.com> Date: Mon, 31 Mar 2014 17:44:55 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <32B6CF01-7D6A-408D-8512-F3D688FB3B59@FreeBSD.org> References: <53111711.1010907@laskoprinting.com> <5318DA3A.8090408@laskoprinting.com> <13A9A291-538E-4A62-B0B2-E6F43BEE7C5B@FreeBSD.org> <53192954.5070707@laskoprinting.com> <1394196776.30615.91728569.21F5ACA3@webmail.messagingengine.com> <5334D5AD.8030800@laskoprinting.com> To: Darren Pilgrim X-Mailer: Apple Mail (2.1874) Sender: feld@feld.me Cc: Scot Hetzel , osa@freebsd.org, FreeBSD Ports , portsmgr@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2014 00:45:11 -0000 On Mar 27, 2014, at 18:51, Darren Pilgrim = wrote: >=20 > I hate to nag about this, but can we get this fixed sometime soon? In = the three weeks since Mark's email, osa updated the port to 1.4.7, but = didn't bother fixing this issue. What happened to this being a showstopp= er in a major port? >=20 Terribly sorry this has taken so long. It appears osa has been AFK and I = have been so busy myself lately that I haven't had time to sit down and = actually look into this. I've now verified that the proposed change does = indeed match the behavior of the nginx-devel identically and the logic = seems sound. The commit is in, sorry it has taken so long. You did the right thing by = sending a reminder. osa, feel free to slap me if this causes any problems for you...