From owner-svn-src-all@freebsd.org Sun Apr 16 16:16:11 2017 Return-Path: Delivered-To: svn-src-all@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 90479D406F1; Sun, 16 Apr 2017 16:16:11 +0000 (UTC) (envelope-from markm@FreeBSD.org) Received: from gromit.grondar.org (grandfather.grondar.org [IPv6:2a01:348:0:15:5d59:5c20:0:2]) (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 5F1731854; Sun, 16 Apr 2017 16:16:11 +0000 (UTC) (envelope-from markm@FreeBSD.org) Received: from graveyard.grondar.org ([88.96.155.33] helo=gronkulator.grondar.org) by gromit.grondar.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88 (FreeBSD)) (envelope-from ) id 1czmqO-0000He-5R; Sun, 16 Apr 2017 17:16:08 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: svn commit: r317015 - in head/sys: boot/forth conf crypto/chacha20 dev/random libkern sys From: Mark R V Murray In-Reply-To: <201704161604.v3GG4aoq017437@pdx.rh.CN85.dnsmgr.net> Date: Sun, 16 Apr 2017 17:16:06 +0100 Cc: src-committers , svn-src-all@FreeBSD.org, svn-src-head@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: <98247B49-8F7C-43D4-A187-54FD6E93DB05@FreeBSD.org> References: <201704161604.v3GG4aoq017437@pdx.rh.CN85.dnsmgr.net> To: rgrimes@FreeBSD.org X-Mailer: Apple Mail (2.3273) X-SA-Score: -1.0 X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 16 Apr 2017 16:16:11 -0000 > On 16 Apr 2017, at 17:04, Rodney W. Grimes = wrote: > So you can understand me being started when any of this arrived? I am > on several of the mailling list, and I think -security is probably one > of them. I was thoroughly ignored last time I tried to use -security. It was, = however, a while back. I'll try again. > What watch list is this? And do we have a watch list that is just = "New Phabricator > created" so we can make just that incident go to some mailling list so = people stop > getting caught off guard by commits that have been reviews that they = wish they had > even known there was a review? We just need a way for being allerted = there is a > new review that we *might* be interested, or care to participate in = without being > on all the watch lists. There is 'secteam' on Phabricator. > And to add my hidden Blue Paint, we need to stop fearing the bike = shed, the project > seems to have stifled the communications process to the point it is = becoming a > closed door shop with everyone working in secret then dumping a commit = in once they > are done. Yes, bike sheds are a bit time consuming, but so is = duplicate work cause > you had no idea someone else was working in the same area (your LKM = suprize is > an excellent example). > We must stop working in vacuums and start to communicate, and if that = means we > have a few bike sheds... well.. paints on me (though I reserve the = blue for=20 > personal use!) Can't please everybody, but I'll add -security to the list next time. There is a fair bit of history that predates your return to the project; = me getting attention to folks prepared to do reviews is a sore point. I use = Phabricator because it works for me (I get reviews). I was largely ignored on the mailing = lists last time I had a big commit.=20 M --=20 Mark R V Murray