From owner-freebsd-current@freebsd.org Wed Jul 12 01:24:33 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16470DB0076; Wed, 12 Jul 2017 01:24:33 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (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 A350373222; Wed, 12 Jul 2017 01:24:31 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190f-2fbff70000003f98-41-5965791ad7be Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 7B.D0.16280.A1975695; Tue, 11 Jul 2017 21:19:23 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id v6C1JLaD017718; Tue, 11 Jul 2017 21:19:22 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v6C1JI19002367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 11 Jul 2017 21:19:21 -0400 Date: Tue, 11 Jul 2017 20:19:18 -0500 From: Benjamin Kaduk To: Rick Macklem Cc: "freebsd-current@freebsd.org" , "rc@freebsd.org" Subject: Re: small patch for /etc/rc.d/nfsd, bugfix or POLA violation? Message-ID: <20170712011918.GB80947@kduck.kaduk.org> References: <201707092031.v69KVBSn045623@slippy.cwsent.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLIsWRmVeSWpSXmKPExsUixG6noitdmRpp8Owqu8WcNx+YLH6t/stk 8XDZNSYHZo8Zn+azePzevJcpgCmKyyYlNSezLLVI3y6BK2Nx6zbGgibmigMv9rI1MK5k6mLk 5JAQMJF4tGYVkM3FISSwmEnibscsNghnI6PEv4VHGCGcq0wSHT3fWUFaWARUJc4cnAFmswmo SDR0X2YGsUUE1CU2r+4Hs5kFsiWu3f0LZgsLuEnsuLqAEcTmBVr391E7K8TQX4wSLSeuMUEk BCVOznzCAtGsJXHj30ugOAeQLS2x/B8HSJhTIFaiY+M+dhBbVEBZ4u/heywTGAVmIemehaR7 FkL3AkbmVYyyKblVurmJmTnFqcm6xcmJeXmpRbomermZJXqpKaWbGEEhyynJv4NxToP3IUYB DkYlHt6GCymRQqyJZcWVuYcYJTmYlER5d+SnRgrxJeWnVGYkFmfEF5XmpBYfYpTgYFYS4Y19 AFTOm5JYWZValA+TkuZgURLnFddojBASSE8sSc1OTS1ILYLJynBwKEnw6lcADRUsSk1PrUjL zClBSDNxcIIM5wEa7h0NVMNbXJCYW5yZDpE/xajL0fRhyxcmIZa8/LxUKXFeZZBBAiBFGaV5 cHNAqUYie3/NK0ZxoLeEeQ+XA1XxANMU3KRXQEuYgJasyQb5oLgkESEl1cBYda1Fttn9tPZj 1dwjqmJ+Ux8cZKwIjA+8uklY4u1Zab/6tb0ROYE769KO9d1NvFzTcZP/esU1LTY9vpu3Dkmf F1P4nH/z6v1Jn9K4vkxzW1nfMaPf/r9huHO+w7cDEZJcjnmHn55xudgwSUSqueNDlJ1RtELU hXixlNPFcpaKl3TjoiwufFdiKc5INNRiLipOBADkBpt4EAMAAA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 12 Jul 2017 01:24:33 -0000 On Tue, Jul 11, 2017 at 11:48:55AM +0000, Rick Macklem wrote: > Cy Schubert wrote: > > > >How about a warning message + an UPDATING entry + no MFC? And, relnotes = > >yes to say we now support RFC7530 in 12.0? > Sounds fine to me. I'll wait to see if there are more comments. Yes, this seems like the sort of thing best done on a major version boundary and not MFC'd. -Ben