Committer guide: generalise review
Some reviews go to other places. Just mention review in general.
This commit is contained in:
parent
205241edc8
commit
4e00cf8428
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=51851
1 changed files with 1 additions and 1 deletions
|
@ -2667,7 +2667,7 @@ Relnotes: yes</programlisting>
|
||||||
</note>
|
</note>
|
||||||
|
|
||||||
<para>If there is any doubt about a commit for any reason at all,
|
<para>If there is any doubt about a commit for any reason at all,
|
||||||
have it reviewed by <literal>-hackers</literal> before
|
have it reviewed before
|
||||||
committing. Better to have it flamed then and there rather than
|
committing. Better to have it flamed then and there rather than
|
||||||
when it is part of the repository. If a commit does results in
|
when it is part of the repository. If a commit does results in
|
||||||
controversy erupting, it may be advisable to consider backing
|
controversy erupting, it may be advisable to consider backing
|
||||||
|
|
Loading…
Reference in a new issue