This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Add myself to MAINTAINERS


Gerald Pfeifer wrote:
"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 you should
check out a tree with SVN using the instructions below and add yourself
to the MAINTAINERS file.  Having done this, you should produce a diff to
this file and circulate it to the <code>gcc-patches<code> list, whilst also
checking in your change to test write access.  For all other changes, please
be sure to follow the write access policies below."

I like this.


I'd prefer to omit "with SVN" (which will make the migration easier in case we switch version control systems at some point in the future) and
would omit the two occurrences of "you should", but these are only two
minor nits. Thanks for the patch!

I've adjusted the wording a little; here is the exact patch.


OK to commit?

Mark


Index: svnwrite.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/svnwrite.html,v retrieving revision 1.11 diff -U3 -r1.11 svnwrite.html --- svnwrite.html 18 May 2006 11:57:24 -0000 1.11 +++ svnwrite.html 24 May 2006 08:29:28 -0000 @@ -46,9 +46,14 @@ <code>ssh-keygen</code> program) and other details.</p>

 <p>Once we have this information we will set up an account on
-gcc.gnu.org and inform you by mail.  At this point you
-should be able to check out a tree with SVN and add yourself to the
-MAINTAINERS file to test write access, following the instructions below.</p>
+<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>

 <hr />
 <h2><a name="setup">Setting up your local SVN tree</a></h2>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]