Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Masaki Muranaka <monaka@monami-software.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Build failure sim/rx on OSX.
Date: Sun, 14 Feb 2010 06:53:00 -0000	[thread overview]
Message-ID: <DCCEF52D-817F-4E93-B6BE-744D13C6F4C9@monami-software.com> (raw)
In-Reply-To: <20100201075737.GQ26827@adacore.com>

Hello Joel and maintainers,

I added myself to MAINTAINERS with a help from Joel Brobecker.  
I'll apply some patches that were already approved soon.

Thanks,

- - - -
2010-02-14  Masaki Muranaka  <monaka@monami-software.com>

	* MAINTAINERS: Add myself for write after approval privileges.
- - - -
Index: MAINTAINERS
===================================================================
RCS file: /cvs/src/src/gdb/MAINTAINERS,v
retrieving revision 1.433
diff -u -p -r1.433 MAINTAINERS
--- MAINTAINERS	21 Dec 2009 10:27:21 -0000	1.433
+++ MAINTAINERS	14 Feb 2010 06:40:12 -0000
@@ -622,6 +622,7 @@ Wu Zhou						woodzltc@cn.ibm.com
 Yoshinori Sato					ysato@users.sourceforge.jp
 Hui Zhu						teawater@gmail.com
 Sergio Durigan Junior				sergiodj@linux.vnet.ibm.com
+Masaki Muranaka					monaka@monami-software.com
 
 
 			Past Maintainers
- - - -
On 2010/02/01, at 16:57, Joel Brobecker wrote:

>> I received assignment forms (cgen/binutils/gdb/gcc) last weekend.
>> And I sent back them today.
>> My name will be registered within this month.
> 
> Great. Depending on snail mail, I'd say that you're about a week away
> from being done.  When the FSF sends you a confirmation, please go to
> http://www.sourceware.org/cgi-bin/pdw/ps_form.cgi to request an accout,
> so that you can start committing changes yourself. You may list me as
> your sponsor.  Once this is done, we'll test your new access by having
> you commit a change to gdb/MAINTAINERS, by adding yourself to the
> WRITE AFTER APPROVAL list (this change is pre-approved/obvious, but
> please remember to send the usual email to gdb-patches with the diff
> and ChangeLog entry to gdb-patches, just like we do for all GDB patches).
> If this all goes well, then you may commit all approved patches - just
> remember again to send confirmation on this list for each patch
> committed, especially since it may have been a while since we approved
> them.
> 
> -- 
> Joel
> 


  reply	other threads:[~2010-02-14  6:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-30  2:23 Masaki Muranaka
2010-02-01  7:19 ` Joel Brobecker
2010-02-01  7:29   ` Masaki Muranaka
2010-02-01  7:58     ` Joel Brobecker
2010-02-14  6:53       ` Masaki Muranaka [this message]
2010-02-14  7:40   ` Masaki Muranaka
2010-02-02  1:43 ` DJ Delorie
2010-02-02  2:57   ` Masaki Muranaka

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=DCCEF52D-817F-4E93-B6BE-744D13C6F4C9@monami-software.com \
    --to=monaka@monami-software.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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