From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: "overseers@sourceware.org" <overseers@sourceware.org>,
Chao-Ying Fu <Chao-Ying.Fu@imgtec.com>
Subject: Re: Request from Chao-ying Fu
Date: Wed, 01 May 2013 00:21:00 -0000 [thread overview]
Message-ID: <20130501002057.GA3781@ednor.casa.cgf.cx> (raw)
In-Reply-To: <81D57523CB07B24881D63DE650C6ED82ED5F82@bamail02.ba.imgtec.org>
On Tue, Apr 30, 2013 at 11:07:20PM +0000, Chao-Ying Fu wrote:
>Christopher Faylor wrote:
>> [mailto:cgf-use-the-mailinglist-please@sourceware.org]
>> Sent: Tuesday, April 30, 2013 3:56 PM
>> To: overseers@sourceware.org; Chao-Ying Fu
>> Subject: Re: Request from Chao-ying Fu
>>
>> On Tue, Apr 30, 2013 at 10:31:03PM -0000,
>> Chao-Ying.Fu@imgtec.com wrote:
>> >Chao-ying Fu would like to be added to sourceware.org.
>> >
>> >For more information, check out:
>> >http://sourceware.org/cgi-bin/pdw/queue.cgi
>> >
>> >Or, check the specific request here:
>> >http://sourceware.org/cgi-bin/pdw/details.cgi?file=5102162.21725
>>
>> 1) You already have an account on sourceware.org.
>>
>> 2) I believe that the rules are that you need to get permission from
>> Nick Clifton for checkin privileges to binutils.
>>
>
>Hi Overseers,
>
> I have write permission to GCC and Binutils projects for many years.
>I was able to use chaoyingfu@sources.redhat.com to contribute to both projects.
>
> However, since few months ago I cannot use the redhat account.
>And both chaoyingfu@sourceware.org and chaoyingfu@gcc.gnu.org don't work, either.
The system hasn't been sources.redhat.com for some time.
What you're actually trying to communicate is that you're having
problems accessing CVS. You've confused things by trying to issue
a new account request rather than ask for your key to be updated.
>Ex:
># cvs -z9 -d chaoyingfu@sourceware.org:/cvs/src co binutils
>Permission denied (publickey).
>cvs [checkout aborted]: end of file from server (consult above messages if any)
>
># cvs -z9 -d chaoyingfu@gcc.gnu.org:/cvs/src co binutils
>Permission denied (publickey).
>cvs [checkout aborted]: end of file from server (consult above messages if any)
>
>Could you help to fix my account issue? And help to update my ssh
>public key with this file.
I've installed the new key. You can update this yourself in the future via:
ssh sourceware.org updatekey < id_rsa.pub
(assuming that you haven't destroyed your old key)
You can also find out if sourceware.org understands your key via:
ssh sourceware.org alive
next prev parent reply other threads:[~2013-05-01 0:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 22:31 Chao-Ying.Fu
2013-04-30 22:56 ` Christopher Faylor
2013-04-30 23:07 ` Chao-Ying Fu
2013-05-01 0:21 ` Christopher Faylor [this message]
2013-05-01 0:28 ` Chao-Ying Fu
-- strict thread matches above, loose matches on Subject: below --
2005-11-18 1:47 fu
2005-08-24 1:02 fu
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=20130501002057.GA3781@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=Chao-Ying.Fu@imgtec.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).