From owner-cvs-ports@FreeBSD.ORG Thu Nov 17 16:40:40 2005 Return-Path: X-Original-To: cvs-ports@FreeBSD.org Delivered-To: cvs-ports@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F5FC16A428; Thu, 17 Nov 2005 16:40:40 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 512C843D46; Thu, 17 Nov 2005 16:40:40 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 528A92FD7; Thu, 17 Nov 2005 10:40:39 -0600 (CST) Date: Thu, 17 Nov 2005 10:40:39 -0600 To: Alexey Dokuchaev Message-ID: <20051117164039.GA31243@soaustin.net> References: <200511171051.jAHApSWX074582@repoman.freebsd.org> <20051117133108.GA29488@FreeBSD.org> <1132234974.79514.12.camel@localhost> <20051117135427.GA34190@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051117135427.GA34190@FreeBSD.org> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: cvs-ports@FreeBSD.org, Pav Lucistnik , cvs-all@FreeBSD.org, ports-committers@FreeBSD.org, Edwin Groothuis Subject: Re: cvs commit: ports/games/quake2lnx Makefile distinfo pkg-message pkg-plist ports/games/quake2lnx/files extra-patch-src_rogue_g__local.h extra-patch-src_rogue_q__shared.c extra-patch-src_xatrix_q__shared.c patch-Makefile patch-src::game::g_phys.c patch-src::linux::gl_glx.c patch-src::linux::rw_in_svgalib.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: Thu, 17 Nov 2005 16:40:40 -0000 On Thu, Nov 17, 2005 at 01:54:27PM +0000, Alexey Dokuchaev wrote: > > So why have you not handled the PR yourself? Is 36 days really not > > enough to sort out a single port PR? > > I can tolerate "maintainer timeout" for really inactive committer, but > not for someone doing commits and being active in the lists. Then you should have put the PR into 'suspended' and/or somehow indicated that you were working on an alternative solution to the problem. portmgr has been fairly lax with the 2-week and 3-month timeouts but IMHO this is also part of the reason we have several hundred PRs that just sit in GNATS forever. I have slowly been working through the backlog and intend to do more. We do have a number of maintainers who ignore certain of their ports while staying active in other areas and there is no external way of telling the difference between 'I have objections to this change' and 'I am ignoring this change' other than email or GNATS. The bottom line is that if people want to flag changes like this they are well advised to use 'suspended'. mcl