From: Chao-ying Fu <cfu@wavecomp.com>
To: "overseers@sourceware.org" <overseers@sourceware.org>
Subject: SSH public key replacement
Date: Wed, 27 Jan 2021 19:59:37 +0000 [thread overview]
Message-ID: <SJ0PR22MB2720B8387C8A1DF9E95217A0D1BB9@SJ0PR22MB2720.namprd22.prod.outlook.com> (raw)
In-Reply-To: <CO6PR22MB27051869CFC96F74DD56C00AD1BB9@CO6PR22MB2705.namprd22.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
Hello,
This is Chao-ying Fu at Wave Computing. I will start to contribute patches to Binutils, GCC, and GDB. I have an account chaoyingfu@sourceware.org since 10+ years ago. However, I cannot use ssh to access Binutils or GCC git now. I guess my old key is lost or my old key is unsecured.
Could you help to replace my public ssh key?
Thanks a lot!
Best Regards,
Chao-ying Fu
________________________________
From: Craig Topham via RT <copyright-clerk@fsf.org>
Sent: Tuesday, January 26, 2021 3:14 PM
To: Chao-ying Fu <cfu@wavecomp.com>
Subject: [EXTERNAL][gnu.org #1674130] Copyright assignment form
On 2021-01-25 19:00:49, cfu@wavecomp.com wrote:
> Hi Craig,
>
> Yes, several people from Wave Computing contributed patches to GCC and
> other projects in 2019. However, those people are not with the company
> any more.
>
> Does the copyright assignment cover all employees from Wave Computing
> to contribute patches?
The Wave Computing copyright assignment can cover all employees, if the code is written as a part of the employees work.
> If not, could you help to add "Chao-ying Fu" to the list?
'Who' and 'how' Wave Computing allows their employers to contribute is entirely up to them. Please let me know if you have any question.
~Craig
> And, I will need an account to set up the ssh key.
>
> Thanks a lot!
>
> Best Regards,
> Chao-ying Fu
[-- Attachment #2: id_rsa.pub --]
[-- Type: application/vnd.ms-publisher, Size: 742 bytes --]
parent reply other threads:[~2021-01-27 19:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CO6PR22MB27051869CFC96F74DD56C00AD1BB9@CO6PR22MB2705.namprd22.prod.outlook.com>]
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=SJ0PR22MB2720B8387C8A1DF9E95217A0D1BB9@SJ0PR22MB2720.namprd22.prod.outlook.com \
--to=cfu@wavecomp.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).