public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: overseers@gcc.gnu.org
Cc: Matt Thomas <matt@3am-software.com>,
	John David Anglin <dave.anglin@nrc-cnrc.gc.ca>
Subject: Write-after-approval commit access for GCC
Date: Mon, 23 Jul 2012 12:32:00 -0000	[thread overview]
Message-ID: <20120723123209.GJ21845@lug-owl.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]

Hi!

I'd like to request commit rights for GCC.  My key is already set-up
(initially for binutils, as a maintainer for the vax-linux port), and
these days, I've sent another patch (for frv-linux), which is
approved.  Nick Clifton will probably commit that for me (as a FRV
port maintainer.)

However, I'll hopefully do more GCC hacking (for the vax-linux
target), so I'd like to get commit-after-approval rights, which I
guess would ease the workflow as seen on the gcc-patches mailling
list.  Copyright assignment papers should be in place (initially
submitted for binutils maintainership) for binutils, gcc and glibc.

Back then, IIRC Matt Thomas <matt@3am-software.com> sponsored me
becoming a VAX maintainer (for binutils), so I hope he will sponsor it
right now, too. Maybe also John David Anglin <dave.anglin@nrc-cnrc.gc.ca>,
who gave up VAX maintainership in August 2008. (But as said: Right
now, I'm only applying for commit-after-approval.  If Matt and/or Dave
would like it, I'd also volunteer as a co-maintainer. For the
Linux-specific bits submitted by others, Matt waited for me to ACK
them in the past.)

Thanks,
Jan-Benedict

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:              Fortschritt bedeutet, einen Schritt so zu machen,
the second  :                   daß man den nächsten auch noch machen kann.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2012-07-23 12:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23 12:32 Jan-Benedict Glaw [this message]
2012-07-24  5:36 ` Hans-Peter Nilsson
2012-07-24  6:16   ` Matt Thomas
2012-07-24 12:02   ` Frank Ch. Eigler
2012-07-24 13:53     ` Jan-Benedict Glaw

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=20120723123209.GJ21845@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=matt@3am-software.com \
    --cc=overseers@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).