From owner-svn-src-all@freebsd.org Mon Mar 5 17:19:19 2018 Return-Path: Delivered-To: svn-src-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 86C5BF40EF7; Mon, 5 Mar 2018 17:19:19 +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 156168476D; Mon, 5 Mar 2018 17:19:18 +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 C41D9EA8; Mon, 5 Mar 2018 11:19:17 -0600 (CST) Date: Mon, 5 Mar 2018 11:19:16 -0600 From: Mark Linimon To: Mark Johnston Cc: Mariusz Zaborski , svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r325739 - in head: lib/libcasper/services lib/libcasper/services/cap_syslog share/mk Message-ID: <20180305171916.GA2359@lonesome.com> References: <201711120834.vAC8YQUq006611@repo.freebsd.org> <20180305161358.GA704@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180305161358.GA704@raichu> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 17:19:19 -0000 On Mon, Mar 05, 2018 at 11:13:58AM -0500, Mark Johnston wrote: > The growing divergence with stable/11 makes it rather painful to > maintain a port, depending on libcasper, that aims to work on both 11 > and head. Even an MFC won't help you, in the medium-term. e.g. via https://www.freebsd.org/security/#sup, even if the MFC made it into 11.2, you would still have several months of supporting the old one. (The FreeBSD package builds are based on the oldest supported point release from a branch.) The current estimate for 11.2 is late June. mcl