From owner-freebsd-ports@FreeBSD.ORG Tue Jul 1 20:00:41 2008 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B45D7106564A for ; Tue, 1 Jul 2008 20:00:41 +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 8E7CB8FC1A for ; Tue, 1 Jul 2008 20:00:41 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: by syn.atarininja.org (Postfix, from userid 1001) id 263DC5C2E; Tue, 1 Jul 2008 16:02:10 -0400 (EDT) Date: Tue, 1 Jul 2008 16:02:10 -0400 From: Wesley Shields To: Jo Rhett Message-ID: <20080701200210.GB13558@atarininja.org> References: <20080701192524.GA13558@atarininja.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080701192524.GA13558@atarininja.org> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: ports@freebsd.org Subject: Re: please commit 124993 for cfengine-2.2.7 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: Tue, 01 Jul 2008 20:00:41 -0000 On Tue, Jul 01, 2008 at 03:25:24PM -0400, Wesley Shields wrote: > On Tue, Jul 01, 2008 at 11:48:42AM -0700, Jo Rhett wrote: > > cfengine hasn't had any updates for over a year now, as the maintainer > > is AWOL. I keep submitting patches but nobody commits them. > > > > The last update to 124993 contains a clean single patch from the > > current ports tree to 2.2.7. Can someone please commit this? > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=124993 > > I will take this one and get it addressed. The PR you are quoting has > not been around long enough for a maintainer timeout, but the other PR > you reference[1] has. I suspect this is not an acceptable condition to > override the maintainer. For now I will put it in my name and address > it once I know the appropriate course of action (wait for maintainer > timeout or if the old timeout applies to this one as well). On second thought I'm going to commit these soon (where by I mean sometime in the next 24 hours hopefully), since the latest PR should have been a followup to the original and as such falls under the maintainer timeout. -- WXS