From owner-svn-ports-all@freebsd.org Sun May 27 19:38:32 2018 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B84EBF7E0C5; Sun, 27 May 2018 19:38:32 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 65B186AECF; Sun, 27 May 2018 19:38:32 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id C166B282; Sun, 27 May 2018 14:38:30 -0500 (CDT) Date: Sun, 27 May 2018 14:38:29 -0500 From: Mark Linimon To: Jan Beich Cc: Martin Wilke , svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r470941 - in head/multimedia: vdr-plugin-eepg vdr-plugin-epgsearch vdr-plugin-extrecmenu vdr-plugin-osdpip vdr-plugin-sleeptimer vdr-plugin-ttxtsubs vdr-plugin-vdrmanager vdr-plugin-vns... Message-ID: <20180527193829.GA9450@lonesome.com> References: <201805261819.w4QIJaMG031420@repo.freebsd.org> <20180527090549.GA7685@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 May 2018 19:38:32 -0000 On Sun, May 27, 2018 at 07:52:32PM +0200, Jan Beich wrote: > - Arbitrary old -CURRENT/-STABLE snapshots are not supported[1] The commits in question were 10 and 8 weeks ago respectively. That doesn't seem long. And yes, both of the former portmgrs you are addressing in your email understand the support policies :-) mcl