From: "Cui, Lili" <lili.cui@intel.com>
To: "overseers@sourceware.org" <overseers@sourceware.org>
Subject: RE: Welcome to sourceware.org
Date: Fri, 3 Apr 2020 06:40:32 +0000 [thread overview]
Message-ID: <eb4ccb03eb7f4a57a493bb2cfd2a8d53@intel.com> (raw)
In-Reply-To: <20200402160227.0991B388A01F@sourceware.org>
Hi overseers,
I got the mail that I have account on sourceware.org,
but I "git clone git+ssh://cuilili@sourceware.org/git/binutils-gdb.git binutils/" failed.
Like :
lilicui@shgcc10:~/project/update_binutils_gitlab$ git clone git+ssh://cuilili@sourceware.org/git/binutils-gdb.git binutils
Cloning into 'binutils'...
cuilili@sourceware.org: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I wonder if I mis copy my publickey, this is my public key. Thank you so much.
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDMPPn/Y6WUuZ+oNxo+n44yvrgZ7ejsuNmcetQtWWnVxwsABZcVy5N4cC751ki4MKOFSM71SRdioiPtvyfqZkqnLfg1bZ8Q8rR3R0Uk7RC5o+5GtJ4jrG/Db7QCVaOSavyd5KgCiBBP5wzwf1FP6zbLYO9PIv6lbB7N/vY4EWaN7bhMPjuv/nlV3/AK89v0x3EoS+Ng7xBrgvD4PY9kIoTci7ihwnRE5Wxv6cgIgux/lm9sPCdUcw+GgL5ZDMUzP//9VrkjH/8DkV/cUjm1BssAjjMZ3pb1cxLfJ6ryG2o9eKJDzmye9I+j8LnzCKLOJDRGOIxwwdj6x+w71W8pRctf lilicui@shgcc10
Lili.
> -----Original Message-----
> From: root <root@sourceware.org>
> Sent: Friday, April 3, 2020 12:02 AM
> To: cuilili@sourceware.org
> Cc: Lu, Hongjiu <hongjiu.lu@intel.com>
> Subject: Welcome to sourceware.org
>
> Your account on sourceware.org is now active. The login name is "cuilili".
> Mail sent to that address is forwarded to lili.cui@intel.com. This forwarding
> is a convenience so that people who reply directly to source control commit
> mail notes will not get a bounce. This is not intended as a general mail
> account. Please do not advertise it.
>
> If your involvement with the project ends at some point, the mail address
> will become invalid and I will laugh evilly as people try in vain to reach you.
> We do track these things.
>
> You should now have write access to the source control repository for your
> project. Presumably you know where things are and how to access them. If
> not, check with your project web page and with the person who sponsored
> you.
>
> You have restricted (not login!) ssh access to the system so if at some point
> you wish to update your ssh key, you can do so with the following
> command:
>
> ssh sourceware.org appendkey < publickeyfile
>
> This will append 'publickeyfile' (usually ~/.ssh/id_dsa.pub or
> ~/.ssh/id_rsa.pub) to your existing allowed ssh keys. If you have entirely lost
> your old ssh key, then grovel to overseers@sourceware.org and someone
> may take pity on you. If you suspect your key has been compromised, let
> the overseers know as soon as possible.
>
> You can also update your email forwarding with the command:
>
> ssh sourceware.org email your@newmail.com
>
> If you have questions, please do not reply to this email. Ask your project
> mailing list.
next parent reply other threads:[~2020-04-03 6:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200402160227.0991B388A01F@sourceware.org>
2020-04-03 6:40 ` Cui, Lili [this message]
2020-04-03 11:16 ` Frank Ch. Eigler
[not found] <20110723180027.5293.qmail@sourceware.org>
2011-07-28 0:19 ` Philippe Waroquiers
2011-07-28 0:23 ` Frank Ch. Eigler
[not found] <20100803203035.19633.qmail@sourceware.org>
2010-08-05 23:10 ` Quentin Neill
2010-08-06 8:30 ` Hans-Peter Nilsson
2010-08-06 13:28 ` Christopher Faylor
2010-08-06 16:46 ` Quentin Neill
2010-08-06 17:22 ` Christopher Faylor
2010-08-06 18:22 ` Quentin Neill
2010-11-09 21:59 ` Quentin Neill
2010-11-16 21:02 ` Quentin Neill
2010-11-17 6:54 ` Ian Lance Taylor
2010-11-17 15:05 ` Sebastian Pop
2010-11-18 4:58 ` Ian Lance Taylor
2010-11-18 21:01 ` Quentin Neill
2010-11-17 0:18 ` Quentin Neill
[not found] <20080322164357.32125.qmail@sourceware.org>
2008-03-22 19:17 ` Chris Demetriou
2008-03-22 20:05 ` Daniel Jacobowitz
2008-03-22 21:57 ` Christopher Faylor
2008-03-24 16:38 ` Chris Demetriou
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=eb4ccb03eb7f4a57a493bb2cfd2a8d53@intel.com \
--to=lili.cui@intel.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).