Date: Thu, 17 Jan 2008 10:08:41 -0500 From: Wesley Shields <wxs@FreeBSD.org> To: Vladimir Zorin <vladimir@braveduck.spb.ru> Cc: Bill Moran <wmoran@potentialtech.com>, freebsd-ports@freebsd.org Subject: Re: bsd.php.mk suggestion Message-ID: <20080117150841.GC8192@atarininja.org> In-Reply-To: <478F6BC6.8030507@braveduck.spb.ru> References: <478F1FED.803@peterhost.ru> <478F5F83.3060508@gmx.de> <20080117094252.27243aee.wmoran@potentialtech.com> <478F6BC6.8030507@braveduck.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 17, 2008 at 05:52:54PM +0300, Vladimir Zorin wrote: > Bill Moran wrote: >> In response to Dominic Fandrey <LoN_Kamikaze@gmx.de>: >> >>> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080117150841.GC8192>