From: law@redhat.com
To: Jason Eckhardt <jle@owlnet.rice.edu>
Cc: overseers@gcc.gnu.org
Subject: Re: Update SSH key request
Date: Fri, 22 Aug 2003 04:59:00 -0000 [thread overview]
Message-ID: <200308220459.h7M4xK9c001366@speedy.slc.redhat.com> (raw)
In-Reply-To: Your message of "Thu, 07 Aug 2003 15:43:24 CDT." <Pine.GSO.4.33.0308071541050.28254-100000@forest.owlnet.rice.edu>
In message <Pine.GSO.4.33.0308071541050.28254-100000@forest.owlnet.rice.edu>, J
ason Eckhardt writes:
>
>I currently have write access to the gcc repository, but I would
>like to update my SSH key. I'd prefer to use the same key that
>is already active for my sources.redhat.com account.
Well, gcc.gnu.org and sources.redhat.com, have the external appearance
of being distinct machines. However, in reality they are one and the
same. Thus the key you use for sources.redhat.com is the same key you
should use for gcc.gnu.org -- nothing special needs to happen for that
(in fact, we would have to go to great lengths to make the keys only
work for one of the two virtual machines and not the other).
Jeff
prev parent reply other threads:[~2003-08-22 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 20:43 Jason Eckhardt
2003-08-07 21:02 ` Christopher Faylor
2003-08-07 22:53 ` Jason Eckhardt
2003-08-22 5:08 ` law
2003-08-22 15:12 ` Jason Eckhardt
2003-08-22 15:32 ` Christopher Faylor
2003-08-22 4:59 ` law [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=200308220459.h7M4xK9c001366@speedy.slc.redhat.com \
--to=law@redhat.com \
--cc=jle@owlnet.rice.edu \
--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).