This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[wwwdocs] svnwrite.html: gcc.gnu.org account vs MAINTAINERS
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: gcc-patches at gcc dot gnu dot org
- Cc: Hariharan Sandanagobalane <hariharans at picochip dot com>
- Date: Sun, 14 Sep 2008 20:31:45 +0200 (CEST)
- Subject: [wwwdocs] svnwrite.html: gcc.gnu.org account vs MAINTAINERS
Given that I had to clean up a dozen or so cases recently, I installed
the following documentation patch: Add a note that the first and last
names on gcc.gnu.org and in the MAINTAINERS need to match.
(The second part of the patch is just reformatting.)
Hari, if you'd like to use the short version of your first name on
gcc.gnu.org, please let me know; otherwise, would you mind using the
longer version in the MAINTAINERS file?
Thanks,
Gerald
Index: svnwrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svnwrite.html,v
retrieving revision 1.16
diff -u -3 -p -r1.16 svnwrite.html
--- svnwrite.html 14 Sep 2008 15:22:29 -0000 1.16
+++ svnwrite.html 14 Sep 2008 18:24:59 -0000
@@ -48,12 +48,15 @@ to supply your SSH public key (which you
<p>Once we have this information we will set up an account on
<code>gcc.gnu.org</code> and inform you by mail. At this point,
check out a tree using the instructions below and add yourself
-to the MAINTAINERS file. 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>
+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.</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>
<hr />
<h2><a name="setup">Setting up your local SVN tree</a></h2>