From: Yao Qi <qiyaoltc@gmail.com>
To: Petr Machata <pmachata@redhat.com>, overseers@sourceware.org
Subject: Re: Request from Petr Machata
Date: Tue, 24 Feb 2015 21:49:00 -0000 [thread overview]
Message-ID: <54ECF1C9.7010308@gmail.com> (raw)
In-Reply-To: <87fv9vyph0.fsf@redhat.com>
On 02/24/2015 09:22 PM, Petr Machata wrote:
> I see, I forgot I did. Is there a way to update my ssh key? I don't
> even know what key there currently is, and can't find anything about it
> in my e-mail.
You've had an account when you worked on frysk project, because
pmachata@sourceware.org had several commits to frysk. Does this help
you to recall what key is used?
>
> Also, is the login pmachata?
Yes, it is.
--
Yao
next prev parent reply other threads:[~2015-02-24 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 0:01 pmachata
2015-02-24 19:04 ` Christopher Faylor
2015-02-24 21:22 ` Petr Machata
2015-02-24 21:49 ` Yao Qi [this message]
2015-02-24 23:35 ` Petr Machata
2015-03-31 10:26 ` Petr Machata
2015-03-31 12:31 ` Ian Lance Taylor
2015-03-31 14:13 ` Petr Machata
2015-03-31 14:12 ` Frank Ch. Eigler
-- strict thread matches above, loose matches on Subject: below --
2007-04-05 17:38 pmachata
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=54ECF1C9.7010308@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=overseers@sourceware.org \
--cc=pmachata@redhat.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).