Date: Tue, 18 Aug 2015 18:42:59 -0500 From: Larry Rosenman <ler@lerctr.org> To: Greg 'groggy' Lehey <grog@freebsd.org> Cc: erwin@freebsd.org, FreeBSD Ports <ports@freebsd.org>, owner-freebsd-ports@freebsd.org Subject: Re: Ports with duplicate LATEST_LINKs Message-ID: <f6f2c6140a2b39afd51b5fce84404667@thebighonker.lerctr.org> In-Reply-To: <20150818231500.GE21491@eureka.lemis.com> References: <201508181237.t7ICbVPZ020613@portsindexbuild.ysv.freebsd.org> <20150818231500.GE21491@eureka.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2015-08-18 18:15, Greg 'groggy' Lehey wrote: > On Tuesday, 18 August 2015 at 12:37:31 +0000, Ports Index build wrote: >> Dear port maintainers, >> >> The following list includes ports maintained by you that have >> duplicate >> LATEST_LINK values. > > Without counting, it looks like a complete list of all ports, > unsorted. Would it be possible to modify the script to send a list of > relevant ports to each committer affected? > > Greg This, apparently, was fallout from LATEST_LINK going away, and the check script not getting the memo...... erwin@'s disabled the nastygram. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f6f2c6140a2b39afd51b5fce84404667>