From owner-freebsd-current@freebsd.org Fri Mar 23 10:44:39 2018 Return-Path: Delivered-To: freebsd-current@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 323A7F5E4B4 for ; Fri, 23 Mar 2018 10:44:39 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BAD6B6CAB8 for ; Fri, 23 Mar 2018 10:44:38 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1ezKBZ-0006ck-Jj; Fri, 23 Mar 2018 11:44:37 +0100 Date: Fri, 23 Mar 2018 11:44:37 +0100 From: Kurt Jaeger To: "Derek (freebsd lists)" <482254ac@razorfever.net> Cc: FreeBSD Current Subject: Re: freebsd-update: to a specific patch level - help please? [PATCH] Message-ID: <20180323104437.GB21001@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 10:44:39 -0000 Hi! > To be clear, *I've included a link to a patch to freebsd-update > in my initial post, and the help I'm looking for: is to get this > functionality added as a feature so others can benefit.* It > works for me already, and I've already benefited. > > (I'm happy to flesh it out, and document it properly, but I'm > very hesitant to spend the time doing it in detail and submitting > a PR if I'm doing this in isolation, and nobody wants it. Please submit this in a PR, and post the PR number here, I'll work to get this in the tree. -- pi@opsec.eu +49 171 3101372 2 years to go !