Date: Mon, 27 May 2019 15:47:11 -0700 (PDT) From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> To: Ian Lepore <ian@freebsd.org> Cc: rgrimes@freebsd.org, Alexey Dokuchaev <danfe@freebsd.org>, Konstantin Belousov <kostikbel@gmail.com>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r232071 - head/sys/vm Message-ID: <201905272247.x4RMlBer012881@gndrsh.dnsmgr.net> In-Reply-To: <b96bcf5fceb677d8996a44fae9217fbff5be4f88.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Mon, 2019-05-27 at 14:34 -0700, Rodney W. Grimes wrote: > > I just ask that before a change be made that starts from some > > static analysis tool that a formal code review occur before > > the change is committed. > > In a word: No. > > We're not talking about some inexperienced coder committing dumb fixes > to silence warnings here. In this specific instance perhaps not so, but unless I am miss remebering the thread either a change was suggested that came from a static analysis tool that an area expert vetoed. That is ineffect what I advocated, so you can say No, but that is not what actually occurred. Furthermore we have had "inexperienced coder's" commit dumb fixes to silence a wwarning that later had to be reverted and cleaned up properly. So again, you can say No, but your basis is wrong. > What I've seen so far is that fixes are > being committed by the people who originally wrote or currently > maintain the code in question. Nothing bad is happening, so nothing > about the process needs to be fixed or changed in any way. This is not what is going on. > Process for process' sake is just obstruction. This is not process for process sake, this is process to stop bad code changes, and you can not say it is not happening, because it is. > -- Ian -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201905272247.x4RMlBer012881>