public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Louis Krupp <louis.krupp@zoho.com>
To: <overseers@gcc.gnu.org>
Subject: Stupid question: access from new system
Date: Tue, 30 Aug 2016 19:56:00 -0000	[thread overview]
Message-ID: <156dd066d70.e0d1c63b38753.4920283002867842373@zoho.com> (raw)

This is a very stupid question.

I haven't done anything for gcc since last November.  Since then, I've bought a new PC (running Fedora 24), the better to build and test on.

I still have write (on approval) access to gcc from my old setup (Fedora 23 on VirtualBox, in the unlikely event that it matters), and I'd like to have the same thing on the new system.  I have my old key files, but I have no recollection of a passphrase.  I have set up key access to my Windows box, for what that's worth.

I'm willing to do a lot of things by trial and error, but playing with ssh keys involving your network isn't one of them.  Any hints you can give me on how to do this would be appreciated.

Louis Krupp

             reply	other threads:[~2016-08-30 19:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 19:56 Louis Krupp [this message]
2016-08-31  0:03 ` 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=156dd066d70.e0d1c63b38753.4920283002867842373@zoho.com \
    --to=louis.krupp@zoho.com \
    --cc=overseers@gcc.gnu.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).