Date: Fri, 14 Mar 2014 11:50:11 +0100 From: John Marino <freebsd.contact@marino.st> To: =?ISO-8859-1?Q?Philippe_Aud=E9oud?= <jadawin@FreeBSD.org> Cc: ports@freebsd.org Subject: Re: FreeBSD ports you maintain which are out of date Message-ID: <5322DEE3.6030604@marino.st> In-Reply-To: <5322DE4E.7090200@marino.st> References: <201403140915.s2E9Fa8I009565@portscout.freebsd.org> <5322CB0E.7000908@marino.st> <20140314093036.GB17905@tuxaco.net> <5322DE4E.7090200@marino.st>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5322DEE3.6030604>