From owner-freebsd-ports@FreeBSD.ORG  Fri Mar 14 10:50:44 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 17B5EE5B;
 Fri, 14 Mar 2014 10:50:44 +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 E49B87D4;
 Fri, 14 Mar 2014 10:50:43 +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 C0F21438BC;
 Fri, 14 Mar 2014 05:50:27 -0500 (CDT)
Message-ID: <5322DEE3.6030604@marino.st>
Date: Fri, 14 Mar 2014 11:50:11 +0100
From: John Marino <freebsd.contact@marino.st>
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?= <jadawin@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>
 <5322DE4E.7090200@marino.st>
In-Reply-To: <5322DE4E.7090200@marino.st>
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 <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Mar 2014 10:50:44 -0000

On 3/14/2014 11:47, John Marino wrote:
> 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?
> 

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.

what about that?
John