From: Palmer Dabbelt <palmer@dabbelt.com>
To: fche@redhat.com
Cc: overseers@sourceware.org
Cc: gerald@pfeifer.com
Subject: Re: Access to the GCC Repositories
Date: Fri, 03 Feb 2017 20:19:00 -0000 [thread overview]
Message-ID: <mhng-4f1ff834-ae05-4bc4-ad9c-70c8a86b3533@palmer-mbp2014> (raw)
In-Reply-To: <20170203200909.GD30208@redhat.com>
On Fri, 03 Feb 2017 12:09:09 PST (-0800), fche@redhat.com wrote:
> Hi -
>
>> I'm going to be maintaining the RISC-V port of GCC as well as
>> binutils, so I'll need access to the repositories. Gerald (CC'd)
>> says he will sponsor me.
>
> Added.
Thanks!
prev parent reply other threads:[~2017-02-03 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 18:48 Palmer Dabbelt
2017-02-03 19:51 ` Gerald Pfeifer
2017-02-03 20:09 ` Frank Ch. Eigler
2017-02-03 20:19 ` Palmer Dabbelt [this message]
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=mhng-4f1ff834-ae05-4bc4-ad9c-70c8a86b3533@palmer-mbp2014 \
--to=palmer@dabbelt.com \
--cc=fche@redhat.com \
--cc=overseers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).