From owner-cvs-ports@FreeBSD.ORG Tue Oct 21 01:19:57 2008 Return-Path: Delivered-To: cvs-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D5661065676; Tue, 21 Oct 2008 01:19:57 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id C50228FC17; Tue, 21 Oct 2008 01:19:56 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.1.91] (S010600132053396e.vc.shawcable.net [24.87.32.150] (may be forged)) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.8) with ESMTP id m9L1Jsi4059356 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Oct 2008 18:19:55 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Message-ID: <48FD2E39.4000603@FreeBSD.org> Date: Mon, 20 Oct 2008 18:19:53 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Jeremy Chadwick References: <200810201626.m9KGQFZx016617@repoman.freebsd.org> <48FCBBC5.4070603@FreeBSD.org> <20081020174908.GA9181@icarus.home.lan> <48FCCAB5.5020208@FreeBSD.org> <48FCCC88.6090009@FreeBSD.org> <20081020213840.GA13440@icarus.home.lan> In-Reply-To: <20081020213840.GA13440@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: cvs-ports@FreeBSD.org, wojtek@wojtek.tensor.gdynia.pl, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/net/asterisk Makefile ports/net/asterisk/files patch-main-utils.c patch-main::utils.c X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2008 01:19:57 -0000 Jeremy Chadwick wrote: > The user and I were discussing, privately, scheduler-related things, and > the PR was mentioned. I told him that ports maintainers are allowed up > to 2 weeks to respond, after which other committers can take over if > need be. After 2 weeks had passed, the user provided me the patch (the > original PR mail snipped his attachment), and I committed it. I still don't see any place where it says that the assigned PR with no activity for more than 2 weeks on it should be considered as an approval request. Just opening PR is not enough IMHO, it's usually task of the requester to contact maintainer and seek for explicit approval if he wants faster turnaround. -Maxim