From owner-freebsd-ports@FreeBSD.ORG Fri Mar 14 10:48:15 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 7736AD26; Fri, 14 Mar 2014 10:48:15 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 50B167AB; Fri, 14 Mar 2014 10:48:14 +0000 (UTC) Received: from [192.168.0.20] (unknown [130.255.19.191]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 5C9BB438BC; Fri, 14 Mar 2014 05:47:59 -0500 (CDT) Message-ID: <5322DE4E.7090200@marino.st> Date: Fri, 14 Mar 2014 11:47:42 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Philippe_Aud=E9oud?= , marino@freebsd.org Subject: Re: FreeBSD ports you maintain which are out of date References: <201403140915.s2E9Fa8I009565@portscout.freebsd.org> <5322CB0E.7000908@marino.st> <20140314093036.GB17905@tuxaco.net> In-Reply-To: <20140314093036.GB17905@tuxaco.net> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: marino@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Mar 2014 10:48:15 -0000 On 3/14/2014 10:30, Philippe Audéoud 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@. Right -- that's why portscout is bombarding the ports@ mail list. If it were maintained we wouldn't see it. > games/doomsday is maintained by ports@. Feel free to make it as ignored > for portscout. Is this the general understanding? Anytime any committer gets annoyed with high-frequency portscout squawks on ports@ we just disable it without asking? John