From: "Frank Ch. Eigler" <fche@elastic.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org, Qing Zhao <QING.ZHAO@oracle.com>
Subject: Re: My account cannot read/write git+ssh://qinzhao@gcc.gnu.org/git/gcc.git
Date: Thu, 8 Oct 2020 09:51:11 -0400 [thread overview]
Message-ID: <20201008135111.GU35820@elastic.org> (raw)
In-Reply-To: <C7AE04DB-DE58-4C18-9B2E-F367DFFB823F@ORACLE.COM>
Hi -
Your replacement ssh public key is now installed.
- FChE
next prev parent reply other threads:[~2020-10-08 13:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 13:46 Qing Zhao
2020-10-08 13:51 ` Frank Ch. Eigler [this message]
2020-10-08 13:52 ` Qing Zhao
2021-10-15 16:44 ` Qing Zhao
2021-10-15 16:59 ` Frank Ch. Eigler
2021-10-15 19:17 ` Qing Zhao
-- strict thread matches above, loose matches on Subject: below --
2020-10-07 14:15 Qing Zhao
2020-10-07 14:17 ` Frank Ch. Eigler
2020-10-07 14:20 ` Qing Zhao
2020-10-07 14:24 ` Frank Ch. Eigler
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=20201008135111.GU35820@elastic.org \
--to=fche@elastic.org \
--cc=QING.ZHAO@oracle.com \
--cc=overseers@gcc.gnu.org \
--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).