From: Andrea Corallo <andrea.corallo@arm.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Ian Lance Taylor <ian@airs.com>,
"overseers@gcc.gnu.org" <overseers@gcc.gnu.org>,
nd <nd@arm.com>
Subject: Re: Gcc repo write access
Date: Thu, 06 Feb 2020 15:06:00 -0000 [thread overview]
Message-ID: <gkreev7rc0a.fsf@arm.com> (raw)
In-Reply-To: <20200206145341.GB1336@redhat.com> (Frank Ch. Eigler's message of "Thu, 6 Feb 2020 09:53:41 -0500")
"Frank Ch. Eigler" <fche@redhat.com> writes:
> Hi -
>
>> > just please give me a feedback when the new key is installed.
>
> installed
>
> - FChE
Great thanks!
Andrea
prev parent reply other threads:[~2020-02-06 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 9:53 Andrea Corallo
2020-01-14 13:38 ` Ian Lance Taylor
2020-01-14 14:09 ` Andrea Corallo
2020-01-16 10:14 ` Andrea Corallo
2020-02-06 8:57 ` Andrea Corallo
2020-02-06 14:53 ` Frank Ch. Eigler
2020-02-06 15:06 ` Andrea Corallo [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=gkreev7rc0a.fsf@arm.com \
--to=andrea.corallo@arm.com \
--cc=fche@redhat.com \
--cc=ian@airs.com \
--cc=nd@arm.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).