From owner-freebsd-ports@FreeBSD.ORG Thu Jan 17 14:59:06 2008 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 1C8C116A419 for ; Thu, 17 Jan 2008 14:59:06 +0000 (UTC) (envelope-from vladimir@braveduck.spb.ru) Received: from braveduck.spb.ru (c253.polustrovo.net [84.204.225.253]) by mx1.freebsd.org (Postfix) with ESMTP id BD03013C469 for ; Thu, 17 Jan 2008 14:59:05 +0000 (UTC) (envelope-from vladimir@braveduck.spb.ru) Received: from [192.168.0.118] (peterweb.spb.ru [85.235.196.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by braveduck.spb.ru (Postfix) with ESMTP id A27C639854; Thu, 17 Jan 2008 17:49:16 +0300 (MSK) Message-ID: <478F6BC6.8030507@braveduck.spb.ru> Date: Thu, 17 Jan 2008 17:52:54 +0300 From: Vladimir Zorin User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: Bill Moran References: <478F1FED.803@peterhost.ru> <478F5F83.3060508@gmx.de> <20080117094252.27243aee.wmoran@potentialtech.com> In-Reply-To: <20080117094252.27243aee.wmoran@potentialtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: bsd.php.mk suggestion 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: Thu, 17 Jan 2008 14:59:06 -0000 Bill Moran wrote: > In response to Dominic Fandrey : > >> Vladimir Zorin wrote: >>> I tried to get in touch with Alex Dupre, the maintainer of the >>> bsd.php.mk, sent him the same text as the above with the patch, but I >>> didn't get any response. As far as I know there are several people who >>> tried to contact him regarding the same issue but, alas, didn't get any >>> response as well. >> I suppose there might be the possibility of a timeout that allows committing >> without Maintainer feedback, if you submit it as a PR. > > This is exactly the way to proceed. > > If the maintainer is not responding, open the issue as a PR so it's > officially tracked. If the maintainer does not respond withing a > reasonable length of time, request a maintainer timeout to have another > committer check in the patch. Thank you for the tip, I'll do the way you described. What regards "reasonable length of time" - a fortnight, for example, is reasonable enough? ------------------- Best regards, Vladimir Zorin