From: Michael Matz <matz@suse.de>
To: David Edelsohn <dje@watson.ibm.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Add myself to MAINTAINERS
Date: Fri, 19 Jul 2002 04:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0207191308230.11313-100000@wotan.suse.de> (raw)
In-Reply-To: <200207182256.SAA26898@makai.watson.ibm.com>
Hi,
On Thu, 18 Jul 2002, David Edelsohn wrote:
> For the ra* files, I think that you are the MAINTAINER. That
> probably is implicit in accepting your work: you need to continue to
> maintain it.
Ok then, when someone OK's this patch I am ;)
Ciao,
Michael.
--
* MAINTAINERS: Add myself as ra* maintainer.
Index: MAINTAINERS
===================================================================
RCS file: /cvs/gcc/gcc/MAINTAINERS,v
retrieving revision 1.224
diff -u -p -r1.224 MAINTAINERS
--- MAINTAINERS 15 Jul 2002 21:17:51 -0000 1.224
+++ MAINTAINERS 19 Jul 2002 11:11:07 -0000
@@ -145,6 +145,7 @@ RTEMS Ports Joel Sherrill
predict.def Jan Hubicka jh@suse.cz
contrib/regression Geoff Keating geoffk@redhat.com
treelang Tim Josling tej@melbpc.org.au
+new regalloc (ra*) Michael Matz matz@suse.de
Note individuals who maintain parts of the compiler need approval to check
in changes outside of the parts of the compiler they maintain.
next prev parent reply other threads:[~2002-07-19 11:11 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 9:08 Patch for warnings in new register allocator code (ra-*.c) Kaveh R. Ghazi
2002-07-18 9:44 ` Michael Matz
2002-07-18 16:06 ` David Edelsohn
2002-07-19 4:54 ` Michael Matz [this message]
2002-07-19 10:24 ` Add myself to MAINTAINERS Richard Henderson
2002-07-18 18:20 ` Patch for warnings in new register allocator code (ra-*.c) Kaveh R. Ghazi
2002-07-21 20:15 ` Kaveh R. Ghazi
2002-11-04 21:26 Add myself to MAINTAINERS Adam Nemet
2002-11-13 10:13 Stuart Hastings
[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-15 6:49 Eric Botcazou
2003-02-24 9:27 Steven Bosscher
2004-01-15 22:55 Daniel Jacobowitz
2005-10-05 13:55 Kaz Kojima
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
2006-05-24 12:38 ` Mark Shinwell
2006-05-24 14:54 ` Gerald Pfeifer
2006-05-18 18:04 ` Nathan Sidwell
2006-09-22 18:57 Fu, Chao-Ying
2007-04-02 7:12 Dave Korn
2007-04-04 6:52 add " Christian BRUEL
2007-05-14 6:43 Thomas Neumann
2007-05-22 20:04 Ollie Wild
2007-07-13 21:45 Add " Dan Hipschman
2007-08-16 12:30 Kai Tietz
2007-09-05 18:43 Pat Haugen
2007-09-17 13:38 Add myself to maintainers Johannes Singler
2008-02-25 14:25 add myself to MAINTAINERS Tomas Bily
2008-04-04 23:46 Add " Andy H
2008-09-21 15:03 Steven Bosscher
2011-06-06 3:14 Nenad Vukicevic
2012-10-03 18:34 Lawrence Crowl
2012-10-24 20:58 Sharad Singhai
2012-10-30 9:21 Gopalasubramanian, Ganesh
2013-07-17 1:31 Tim Shen
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.33.0207191308230.11313-100000@wotan.suse.de \
--to=matz@suse.de \
--cc=dje@watson.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
/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).