From: Richard Earnshaw <[email protected]> Document how to use the new scripts to regenerate the MAINTAINERS data. --- htdocs/gitwrite.html | 29 ++++++++++++++++------------- 1 file changed, 16 insertions(+), 13 deletions(-)
diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html index 72bca381..a939fb15 100644 --- a/htdocs/gitwrite.html +++ b/htdocs/gitwrite.html @@ -43,19 +43,22 @@ href="https://sourceware.org/cgi-bin/pdw/ps_form.cgi";>this form</a>, again specifying your sponsor.</p> <p>We will then provision you and inform you by mail. At this point, -check out a tree using the instructions below and add yourself -to the MAINTAINERS file. Note: Your first and last names <em>must</em> -be exactly the same between your account on gcc.gnu.org and the -MAINTAINERS file. Place your name in the correct section following -the conventions specified in the file (e.g. "Write After Approval" -is "last name alphabetical order"). If you do not have an FSF copyright -assignment on file, also add yourself to the DCO section in the file.</p> - -<p>Then produce a diff to that file and circulate it to the -<code>gcc-patches</code> list, whilst also checking in your change to -test write access (approval from the mailing list is not needed in this -one case). For all other changes, please be sure to follow the write -access policies below.</p> +check out a tree using the instructions below and add yourself to the +MAINTAINERS.yml database. Note: Your first and last names +<em>must</em> be exactly the same between your account on gcc.gnu.org +and the MAINTAINERS.yml entry. A small script in +<code>contrib/add-write-after.py</code> will handle the most common +cases and the result can be post-edited if necessary. If you do not +have an FSF copyright assignment on file, also add a DCO entry.</p> + +<p>Once the MAINTAINERS.yml data is correct, use the script +<code>contrib/gen-MAINTAINERS.py</code> to rebuild the human-readable +MAINTAINERS file (the script will validate the YAML data). Finally, +produce a diff of your changes and circulate it to +the <code>gcc-patches</code> list, whilst also checking in your change +to test write access (approval from the mailing list is not needed in +this one case). For all other changes, please be sure to follow the +write access policies below.</p> <hr> <h2 id="setup">Setting up your local Git tree</h2> -- 2.54.0
