From owner-svn-doc-head@FreeBSD.ORG Sat Jun 28 19:37:33 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9B7444AF; Sat, 28 Jun 2014 19:37:33 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (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 6E4CF21DA; Sat, 28 Jun 2014 19:37:33 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s5SJbXjI034062; Sat, 28 Jun 2014 19:37:33 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s5SJbXZr034061; Sat, 28 Jun 2014 19:37:33 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201406281937.s5SJbXZr034061@svn.freebsd.org> From: Eitan Adler Date: Sat, 28 Jun 2014 19:37:33 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45138 - head/en_US.ISO8859-1/articles/committers-guide X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2014 19:37:33 -0000 Author: eadler Date: Sat Jun 28 19:37:32 2014 New Revision: 45138 URL: http://svnweb.freebsd.org/changeset/doc/45138 Log: The script in ~fenner relies on CVS. I've modified it for svn. In addition, call out that technical conversations should not happen in private. Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/committers-guide/article.xml Sat Jun 28 16:00:56 2014 (r45137) +++ head/en_US.ISO8859-1/articles/committers-guide/article.xml Sat Jun 28 19:37:32 2014 (r45138) @@ -2818,15 +2818,20 @@ Relnotes: yes Makefile. For other parts of the repository, if you are unsure who the active maintainer might be, it may help to scan the revision history to see who has - committed changes in the past. &a.fenner.email; has written a - nice shell script that can help determine who the active - maintainer might be. It lists each person who has committed to + committed changes in the past. An example script that lists + each person who has committed to a given file along with the number of commits each person has - made. It can be found on freefall at - ~fenner/bin/whodid. If your queries go + made can be found at on freefall at + ~eadler/bin/whodid. If your queries go unanswered or the committer otherwise indicates a lack of interest in the area affected, go ahead and commit it. + + Avoid sending private emails to maintainers. Other people + might be interested in the conversation, not just the final + output. + + If you are unsure about a commit for any reason at all, have it reviewed by -hackers before committing. Better to have it flamed then and there rather than when it is