public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Qing Zhao <qing.zhao@oracle.com>
To: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>
Subject: Re: My account cannot read/write git+ssh://qinzhao@gcc.gnu.org/git/gcc.git
Date: Fri, 15 Oct 2021 16:44:32 +0000	[thread overview]
Message-ID: <C4954477-E0C2-40AB-ABEE-22553B971051@oracle.com> (raw)
In-Reply-To: <C7AE04DB-DE58-4C18-9B2E-F367DFFB823F@ORACLE.COM>

Dear administrator,

If I want to clone the git repository:

git+ssh://qinzhao@gcc.gnu.org/git/gcc.git

In a new machine, what should I do?

Can I add the key to the gitlab myself?

Thanks.

Qing

> On Oct 8, 2020, at 8:46 AM, Qing Zhao <qing.zhao@oracle.com> wrote:
> 
> Dear administrator,
> 
> I am trying to clone the write-accessible git repository 
> 
> git+ssh://qinzhao@gcc.gnu.org/git/gcc.git
> 
> Today in order to commit one patch to gcc upstream,
> 
> However I was not able to do it (I have been able to do this previously on other machine):
> 
> qinzhao@gcc10:~/.ssh$ git clone git+ssh://qinzhao@gcc.gnu.org/git/gcc.git gcc
> Cloning into 'gcc'...
> Permission denied (publickey).
> fatal: Could not read from remote repository.
> 
> Please make sure you have the correct access rights
> and the repository exists.
> 
> What’s this issue? How can I resolve it?
> 
> Thanks a lot for your help.
> 
> Qing


  parent reply	other threads:[~2021-10-15 16:44 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
2020-10-08 13:52   ` Qing Zhao
2021-10-15 16:44 ` Qing Zhao [this message]
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=C4954477-E0C2-40AB-ABEE-22553B971051@oracle.com \
    --to=qing.zhao@oracle.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).