os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

The script in ~fenner relies on CVS. I've modified it for svn.

Browse source 
In addition, call out that technical conversations should not happen in
private.
This commit is contained in:
Eitan Adler 2014-06-28 19:37:32 +00:00
parent 250c9d3e4c
commit 88e5278159
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=45138
1 changed files with 10 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
en_US.ISO8859-1/articles/committers-guide/article.xml
View file

@ -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