From: Mike Frysinger <vapier@gentoo.org>
To: overseers@gcc.gnu.org
Cc: jie@codesourcery.com
Subject: request for gcc write access
Date: Sun, 16 Jan 2011 07:46:00 -0000 [thread overview]
Message-ID: <201101160246.35210.vapier@gentoo.org> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 552 bytes --]
i have a sourceware.org account already as "vapier". ive made plenty of
commits to the sourceware.org repo (mostly Blackfin related, but common code
too). i'd like to get write access to the gcc repo for Blackfin (and general)
maintenance purposes. when i post patches to gcc-patches, people tend to ack
and forget as they expect me to make the actual commit. but i cant :(. and
then things stall because no one else feels like taking care of it.
Jie said he would be my sponsor as he already has gcc write access
thanks !
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2011-01-16 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 7:46 Mike Frysinger [this message]
2011-01-16 7:53 ` Jie Zhang
2011-01-17 23:56 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2006-06-29 19:42 Request for GCC Write Access Andrew John Hughes
[not found] ` <20060629194804.GE913@redhat.com>
2006-06-29 20:41 ` Andrew John Hughes
2006-06-29 23:35 ` Christopher Faylor
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=201101160246.35210.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=jie@codesourcery.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).