From owner-freebsd-ports@FreeBSD.ORG Fri Mar 14 14:48:43 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7F83BB49; Fri, 14 Mar 2014 14:48:43 +0000 (UTC) Received: from huppa.tuxaco.net (tuxaco.net [IPv6:2001:41d0:1:66c1::1]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 45813333; Fri, 14 Mar 2014 14:48:43 +0000 (UTC) Received: by huppa.tuxaco.net (Postfix, from userid 1001) id EC0AD2286E; Fri, 14 Mar 2014 15:48:41 +0100 (CET) Date: Fri, 14 Mar 2014 15:48:41 +0100 From: Philippe =?iso-8859-1?Q?Aud=E9oud?= To: marino@freebsd.org Subject: Re: FreeBSD ports you maintain which are out of date Message-ID: <20140314144841.GD17905@tuxaco.net> References: <201403140915.s2E9Fa8I009565@portscout.freebsd.org> <5322CB0E.7000908@marino.st> <20140314093036.GB17905@tuxaco.net> <5322DE4E.7090200@marino.st> <5322DEE3.6030604@marino.st> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <5322DEE3.6030604@marino.st> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Mar 2014 14:48:43 -0000 On Fri, 14 Mar 2014, John Marino wrote: > On 3/14/2014 11:47, John Marino wrote: > > On 3/14/2014 10:30, Philippe Aud=E9oud wrote: > >> On Fri, 14 Mar 2014, John Marino wrote: > >> > >>> On 3/14/2014 10:15, portscout@FreeBSD.org wrote: > >>>> Port | Current version | = New version > >>>> ------------------------------------------------+-----------------+-= ----------- > >>>> games/doomsday | 1.12.2 | = 1.14.0-build1168 > >>>> ------------------------------------------------+-----------------+-= ----------- > >>> > >>> This port squawks constantly. > >>> Can we either get the last submitter to take it over or put it on the > >>> to-be-killed list? Or tell portscout to ignore it? Too much noise on > >>> already high volume channel. > >>> > >>> John > >> > >> Hello John, > >> > >> games/doomsday is maintained by ports@. > >=20 > > Right -- that's why portscout is bombarding the ports@ mail list. If it > > were maintained we wouldn't see it. > >=20 > >> games/doomsday is maintained by ports@. Feel free to make it as ignored > >> for portscout. > >=20 > > Is this the general understanding? Anytime any committer gets annoyed > > with high-frequency portscout squawks on ports@ we just disable it > > without asking? > >=20 >=20 > I thought I caught this before it went out. > I wanted to suggest that maybe portscout can not send any notice to > ports@ by rule if the port is unmaintained. >=20 > what about that? > John It's a good thing we are noticed when ports are outdated for ports@ but I'm fine with your idea to have a remind once a week or a month. Regards, --=20 Philippe Aud=E9oud