Date: Sat, 28 Jun 2014 19:37:33 +0000 (UTC) From: Eitan Adler <eadler@FreeBSD.org> 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 Message-ID: <201406281937.s5SJbXZr034061@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
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</programlisting> <filename>Makefile</filename>. 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 <systemitem>freefall</systemitem> at - <filename>~fenner/bin/whodid</filename>. If your queries go + made can be found at on <systemitem>freefall</systemitem> at + <filename>~eadler/bin/whodid</filename>. If your queries go unanswered or the committer otherwise indicates a lack of interest in the area affected, go ahead and commit it.</para> + <note> + <para>Avoid sending private emails to maintainers. Other people + might be interested in the conversation, not just the final + output.</para> + </note> + <para>If you are unsure about a commit for any reason at all, have it reviewed by <literal>-hackers</literal> before committing. Better to have it flamed then and there rather than when it is
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201406281937.s5SJbXZr034061>