public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Mark Shinwell <shinwell@codesourcery.com>
Cc: Paul Brook <paul@codesourcery.com>,
	gcc-patches@gcc.gnu.org,      Mike Stump <mrs@apple.com>
Subject: Re: Add myself to MAINTAINERS
Date: Sun, 21 May 2006 15:18:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61.0605211627060.19658@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <446DC21F.5050508@codesourcery.com>

On Fri, 19 May 2006, Mark Shinwell wrote:
> How about:

Thanks for the proposal, Mark!

> "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!

Gerald

  reply	other threads:[~2006-05-21 14:30 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18 14:00 Mark Shinwell
2006-05-18 17:30 ` Mike Stump
2006-05-18 17:59   ` Paul Brook
2006-05-18 18:43     ` Mike Stump
2006-05-18 21:58     ` Gerald Pfeifer
2006-05-19 15:37       ` Mark Shinwell
2006-05-21 15:18         ` Gerald Pfeifer [this message]
2006-05-24 12:38           ` Mark Shinwell
2006-05-24 14:54             ` Gerald Pfeifer
2006-05-18 18:04   ` Nathan Sidwell
  -- strict thread matches above, loose matches on Subject: below --
2013-07-17  1:31 Tim Shen
2012-10-30  9:21 Gopalasubramanian, Ganesh
2012-10-24 20:58 Sharad Singhai
2012-10-03 18:34 Lawrence Crowl
2011-06-06  3:14 Nenad Vukicevic
2008-09-21 15:03 Steven Bosscher
2008-04-04 23:46 Andy H
2008-02-25 14:25 add " Tomas Bily
2007-09-17 13:38 Add myself to maintainers Johannes Singler
2007-09-05 18:43 Add myself to MAINTAINERS Pat Haugen
2007-08-16 12:30 Kai Tietz
2007-07-13 21:45 Dan Hipschman
2007-05-22 20:04 add " Ollie Wild
2007-05-14  6:43 Thomas Neumann
2007-04-04  6:52 Christian BRUEL
2007-04-02  7:12 Add " Dave Korn
2006-09-22 18:57 Fu, Chao-Ying
2005-10-05 13:55 Kaz Kojima
2004-01-15 22:55 Daniel Jacobowitz
2003-02-24  9:27 Steven Bosscher
2002-11-15  6:49 Eric Botcazou
     [not found] <4EC87374-F7F7-11D6-BFB6-003065ED8B66@apple.com>
2002-11-14 11:05 ` Mike Stump
2002-11-14 11:43   ` Zack Weinberg
2002-11-14 13:40     ` Gerald Pfeifer
2002-11-13 10:13 Stuart Hastings
2002-11-04 21:26 Adam Nemet
2002-07-18 16:06 Patch for warnings in new register allocator code (ra-*.c) David Edelsohn
2002-07-19  4:54 ` Add myself to MAINTAINERS Michael Matz
2002-07-19 10:24   ` Richard Henderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.61.0605211627060.19658@acrux.dbai.tuwien.ac.at \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mrs@apple.com \
    --cc=paul@codesourcery.com \
    --cc=shinwell@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).