From: Srinath Parvathaneni <Srinath.Parvathaneni@arm.com>
To: "Frank Ch. Eigler" <fche@elastic.org>,
Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
Cc: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>, nd <nd@arm.com>
Subject: Re: Access request to the GCC repository.
Date: Mon, 16 Mar 2020 10:28:06 +0000 [thread overview]
Message-ID: <AM0PR08MB53800D57F8C10C755C6EAE419BF90@AM0PR08MB5380.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20200302121738.GA117529@elastic.org>
[-- Attachment #1: Type: text/plain, Size: 641 bytes --]
Hi Frank,
I forgot my passphrase for my previous ssh key, so I generated a new ssh key.
I'm adding the public ssh key in this file, please add this to git repo.
Regards,
SRI
________________________________
From: Frank Ch. Eigler <fche@elastic.org>
Sent: 02 March 2020 12:17
To: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
Cc: Srinath Parvathaneni <Srinath.Parvathaneni@arm.com>; overseers@gcc.gnu.org <overseers@gcc.gnu.org>; nd <nd@arm.com>
Subject: Re: Access request to the GCC repository.
Hi -
> Can we please enable write access to the GCC git repo for Srinath?
> I am his sponsor.
This is already done.
- FChE
[-- Attachment #2: id_rsa.pub --]
[-- Type: application/vnd.ms-publisher, Size: 410 bytes --]
next prev parent reply other threads:[~2020-03-16 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 15:18 Srinath Parvathaneni
2020-02-17 17:43 ` Christopher Faylor
2020-02-25 16:20 ` Srinath Parvathaneni
2020-02-25 16:28 ` Christopher Faylor
2020-03-02 10:39 ` Kyrylo Tkachov
2020-03-02 12:17 ` Frank Ch. Eigler
2020-03-16 10:28 ` Srinath Parvathaneni [this message]
2020-03-02 15:06 ` 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=AM0PR08MB53800D57F8C10C755C6EAE419BF90@AM0PR08MB5380.eurprd08.prod.outlook.com \
--to=srinath.parvathaneni@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=fche@elastic.org \
--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).