From owner-svn-src-all@freebsd.org Fri Feb 24 14:43:30 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 55902CEB712; Fri, 24 Feb 2017 14:43:30 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 33C31C74; Fri, 24 Feb 2017 14:43:30 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 7BDC72D06; Fri, 24 Feb 2017 14:43:29 +0000 (UTC) Date: Fri, 24 Feb 2017 14:43:29 +0000 From: Alexey Dokuchaev To: Eric van Gyzen Cc: Ngie Cooper , "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , "src-committers@freebsd.org" Subject: Re: svn commit: r314179 - in head: contrib/netbsd-tests/lib/librt include lib/libc/gen lib/libc/include share/man/man3 sys/kern Message-ID: <20170224144329.GA13444@FreeBSD.org> References: <201702231936.v1NJadRa029404@repo.freebsd.org> <31cd29ad-6c34-f3d0-b71c-04857b013d02@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <31cd29ad-6c34-f3d0-b71c-04857b013d02@FreeBSD.org> User-Agent: Mutt/1.7.1 (2016-10-04) 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: Fri, 24 Feb 2017 14:43:30 -0000 On Fri, Feb 24, 2017 at 08:22:21AM -0600, Eric van Gyzen wrote: > By the way, have you considered adding a Herald rule on Phabricator? > Phab is not perfect, but a lot of folks use it, and the Herald rules > are a very effective way to watch them play in one's area. +1, we need more Herald rules to make Phabricator more efficient. Of course there are #manpages or #network groups, but often it is a bit hard to come up with whom you'd want to place on the review list (like if MAINTAINERS does not mention who's responsible and/or willing to review the code you touch, and obviously you don't want to annoy some random people just because you think they are technically qualified enough or have required domain knowledge). Sending "Hey check this out guys, Dxxxx" emails on e.g. -hackers@ is not a good option either (as it would annoy even more people). ./danfe