diff --git a/en_US.ISO8859-1/articles/committers-guide/article.xml b/en_US.ISO8859-1/articles/committers-guide/article.xml
index f4c9cf6798..aee00d8d67 100644
--- a/en_US.ISO8859-1/articles/committers-guide/article.xml
+++ b/en_US.ISO8859-1/articles/committers-guide/article.xml
@@ -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