From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: overseers@sourceware.org, Daniel Gutson <dgutson@codesourcery.com>
Subject: Re: cvs access error
Date: Thu, 13 Aug 2009 01:24:00 -0000 [thread overview]
Message-ID: <20090813012343.GC29193@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4A8340E3.1050109@codesourcery.com>
On Wed, Aug 12, 2009 at 07:23:31PM -0300, Daniel Gutson wrote:
>
>
>Christopher Faylor wrote:
>>>>> Please let me know what I can do in order to get write access to
>>>>> binutils, or what I'm doing wrong.
>>>> I'm guessing that you used the wrong key when you registered. The tag
>>>> on the one you sent to sourceware is daniel-gutson-internal-20080711.
>>> what makes you say it's wrong?
>>
>> I said "I'm guessing".
>
>I know, I just asked because maybe you saw something and I could learn
>it. Np.
>
>>
>> You're using a key called /home/daniel/.ssh/fsf but the key that you
>> registered doesn't have the word 'fsf' in it.
>
>Yes, that's because it was 'id_rsa.pub' and I renamed it to 'fsf.pub',
>and similarly for the private one.
>
>>
>>> Please let me know, I'm no good with this stuff.
>>
>> Sounds like some manual reading is in order.
>>
>>> Do you want me to re-generate a new pair?
>>
>> No. That shouldn't be necessary.
>
>Ok, let's see then how we can solve this.
Can we start with your confirming that the private key your'e using
corresponds to the public key containing the string
daniel-gutson-internal-20080711 ?
cgf
next prev parent reply other threads:[~2009-08-13 1:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 19:34 Daniel Gutson
2009-08-12 20:38 ` Christopher Faylor
2009-08-12 20:49 ` Daniel Gutson
2009-08-12 21:38 ` Christopher Faylor
2009-08-12 22:24 ` Daniel Gutson
2009-08-13 1:24 ` Christopher Faylor [this message]
2009-08-13 1:33 ` Daniel Gutson
2009-08-18 16:23 ` Daniel Gutson
2009-08-19 3:32 ` Ian Lance Taylor
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=20090813012343.GC29193@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=dgutson@codesourcery.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).