Date: Tue, 26 Feb 2019 09:26:04 -0800 From: John Baldwin <jhb@FreeBSD.org> To: "K. Macy" <kmacy@freebsd.org>, Brooks Davis <brooks@freebsd.org> Cc: Matt Macy <mmacy@freebsd.org>, svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers <src-committers@freebsd.org> Subject: Re: svn commit: r344487 - in head/sys: conf gnu/gcov Message-ID: <59e33dc7-cd10-7edd-9ff3-418d3eeef1f2@FreeBSD.org> In-Reply-To: <CAHM0Q_NetD%2BbGqtEYEBj0PKEH-G7VuOaTyFH_wdqZHJG5B7FCg@mail.gmail.com> References: <201902232114.x1NLE0cH085345@repo.freebsd.org> <20190225175809.GB47081@spindle.one-eyed-alien.net> <CAHM0Q_NetD%2BbGqtEYEBj0PKEH-G7VuOaTyFH_wdqZHJG5B7FCg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/25/19 5:11 PM, K. Macy wrote: >> This commit needed more through review. > > How would this be achieved:? I had several people on the review and no > one had substantive feedback. As a developer it is your responsibility to be aware of the policies that we do document. One of the things in the license policy Brooks pointed you at is that adding new GPL code requires core@ sign off. This doesn't mean core@ will say know. It does mean that core@ has to make an explicit decision. (I know Brooks said he intended to update the policy, but in fact it already requires core@ sign off for any new code that isn't following one of the accepted licenses which are all BSD/MIT-style licenses.) -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?59e33dc7-cd10-7edd-9ff3-418d3eeef1f2>