From owner-freebsd-ports@FreeBSD.ORG Thu Jan 17 15:08:07 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 0559416A41A for ; Thu, 17 Jan 2008 15:08:07 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.60.158]) by mx1.freebsd.org (Postfix) with ESMTP id EE98313C45D for ; Thu, 17 Jan 2008 15:08:06 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: by syn.atarininja.org (Postfix, from userid 1001) id C8E105C5A; Thu, 17 Jan 2008 10:08:41 -0500 (EST) Date: Thu, 17 Jan 2008 10:08:41 -0500 From: Wesley Shields To: Vladimir Zorin Message-ID: <20080117150841.GC8192@atarininja.org> References: <478F1FED.803@peterhost.ru> <478F5F83.3060508@gmx.de> <20080117094252.27243aee.wmoran@potentialtech.com> <478F6BC6.8030507@braveduck.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <478F6BC6.8030507@braveduck.spb.ru> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Bill Moran , 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 15:08:07 -0000 On Thu, Jan 17, 2008 at 05:52:54PM +0300, Vladimir Zorin wrote: > 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? The default timeout is 14 days (so yes, a fortnight). In your case it may be longer before it's committed since it's a change to something in Mk. Either way, getting it into GNATS so it can be properly tracked and analyzed by the proper people is the right thing to do. -- WXS