These local styles feel a bit odd to begin with, and if we skip the <p>...</p> within <li>...</li>, the originally perceived/ addresses issue should go away.
Unless there are objections from the Fortran side, I plan on committing this in a couple of days. Gerald Index: fortran/index.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/fortran/index.html,v retrieving revision 1.34 diff -u -r1.34 index.html --- fortran/index.html 29 Jun 2014 11:31:33 -0000 1.34 +++ fortran/index.html 30 Jan 2016 04:02:12 -0000 @@ -91,52 +91,51 @@ people:</p> <ul> -<li><p style="margin-bottom: 0in">Paul Brook</p></li> -<li><p style="margin-bottom: 0in">Steven Bosscher</p></li> -<li><p style="margin-bottom: 0in">Bud Davis</p></li> -<li><p style="margin-bottom: 0in">Jerry DeLisle</p></li> -<li><p style="margin-bottom: 0in">Toon Moene</p></li> -<li><p style="margin-bottom: 0in">Tobias Schlueter</p></li> -<li><p style="margin-bottom: 0in">Janne Blomqvist</p></li> -<li><p style="margin-bottom: 0in">Steve Kargl</p></li> -<li><p style="margin-bottom: 0in">Thomas Koenig</p></li> -<li><p style="margin-bottom: 0in">Paul Thomas</p></li> -<li><p style="margin-bottom: 0in">Janus Weil</p></li> -<li><p style="margin-bottom: 0in">Daniel Kraft</p></li> -<li><p>Daniel Franke</p></li> +<li>Paul Brook</li> +<li>Steven Bosscher</li> +<li>Bud Davis</li> +<li>Jerry DeLisle</li> +<li>Toon Moene</li> +<li>Tobias Schlueter</li> +<li>Janne Blomqvist</li> +<li>Steve Kargl</li> +<li>Thomas Koenig</li> +<li>Paul Thomas</li> +<li>Janus Weil</li> +<li>Daniel Kraft</li> +<li>Daniel Franke</li> </ul> <p>Under the rules specified below: </p> <ul> -<li><p style="margin-bottom: 0in">All <a href="../contribute.html">normal +<li>All <a href="../contribute.html">normal requirements</a> for patch submission (assignment of copyright to the FSF, testing, ChangeLog entries, etc) still apply, and reviewers should ensure that these have been met before approving -changes.</p></li> -<li><p style="margin-bottom: 0in">Approval should be necessary for +changes.</li> +<li>Approval should be necessary for patches which don't fall under the obvious rule. So, with the approver list put in place, everybody (except maintainers) should still seek approval for his/her patches. We have found the mutual peer review process really -works well.</p></li> -<li><p style="margin-bottom: 0in">Patches should only be reviewed by +works well.</li> +<li>Patches should only be reviewed by people who know the affected parts of the compiler. (i.e. the reviewer has to be sure he/she knows stuff well enough to make a -good judgment.)</p></li> -<li><p style="margin-bottom: 0in">Large/complicated patches should -still go by one of our maintainers, or team consensus.</p></li> -<li><p>We are all reasonable people, and nobody is working under +good judgment.)</li> +<li>Large/complicated patches should +still go by one of our maintainers, or team consensus.</li> +<li>We are all reasonable people, and nobody is working under employer pressure or needs an ego-boost badly, so in general we -assume that no-one deliberately does anything stupid :-) </p></li> +assume that no-one deliberately does anything stupid :-)</li> </ul> <p>The directories involved are:</p> <ol> -<li><p style="margin-bottom: 0in">gcc/gcc/fortran/ </p></li> -<li><p style="margin-bottom: 0in">gcc/gcc/testsuite/gfortran.dg/ </p></li> -<li><p style="margin-bottom: 0in">gcc/gcc/testsuite/gfortran.fortran-torture/ -</p></li> -<li><p>gcc/libgfortran/</p></li> +<li>gcc/gcc/fortran/</li> +<li>gcc/gcc/testsuite/gfortran.dg/</li> +<li>gcc/gcc/testsuite/gfortran.fortran-torture/</li> +<li>gcc/libgfortran/</li> </ol> <h2>Documentation</h2>
