From: Carlos O'Donell <codonell@redhat.com>
To: Siva Chandra <sivachandra@google.com>, overseers@sourceware.org
Subject: Re: Resetting my public key and gaining write access to glibc
Date: Thu, 28 Mar 2019 04:17:00 -0000 [thread overview]
Message-ID: <6f462230-1a3d-5b06-1729-2e1f7cd0f4df@redhat.com> (raw)
In-Reply-To: <CAGyQ6gxq-Jq2jYsFA2Ken0cLNfpR3-wNJBYHWbtmvEvfwm9YUg@mail.gmail.com>
On 3/15/19 2:49 PM, Siva Chandra via overseers wrote:
> Hello overseers,
>
> I have a sourceware.org account with username "sivachandra". I have write
> access for binutils-gdb, and would now like to gain write access to glibc.
> I will mainly be committing to the google/* branches.
>
> Since it has been a few years that I last committed to the GDB repo, I have
> lost the public key I set up for it. How do I restore my ssh credentials?
Just to close the loop here I helped Siva.
This should all be resolved now.
--
Cheers,
Carlos.
prev parent reply other threads:[~2019-03-28 4:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 18:50 Siva Chandra via overseers
2019-03-15 20:55 ` Carlos O'Donell
2019-03-18 18:45 ` Stan Shebs via overseers
2019-03-28 4:17 ` Carlos O'Donell [this message]
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=6f462230-1a3d-5b06-1729-2e1f7cd0f4df@redhat.com \
--to=codonell@redhat.com \
--cc=overseers@sourceware.org \
--cc=sivachandra@google.com \
/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).