public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Siva Chandra <sivachandra@google.com>
To: overseers@sourceware.org
Subject: Fwd: Welcome to sourceware.org
Date: Wed, 12 Sep 2012 23:30:00 -0000	[thread overview]
Message-ID: <CAGyQ6gx46ZBagb5rxzoncvdBEMKn1YfDxQSb=MVfkE9X-5fOLA@mail.gmail.com> (raw)
In-Reply-To: <20120321204838.18781.qmail@sourceware.org>

Hello,

Due to a hard drive crash, I lost my ssh key file. Is it possible to
setup a new one?

Thanks,
Siva Chandra

---------- Forwarded message ----------
From:  <zroot@sourceware.org>
Date: Wed, Mar 21, 2012 at 1:48 PM
Subject: Welcome to sourceware.org
To: sivachandra@sourceware.org
Cc: tromey@redhat.com


Your account is now active, the login name is sivachandra@sourceware.org.
Mail sent to that address is forwarded to sivachandra@google.com.
This forwarding is a convenience so that people who reply directly to
source control commit mail notes will not get a bounce.  This is not
intended as a general mail account.  Please do not advertise it.

If your involvement with the project ends at some point, the mail address
will become invalid and I will laugh evilly as people try in vain to
reach you.  We do track these things.

You should now have write access to the source control repository for
your project.  Presumably you know where things are and how to access
them.  If not, check with your project web page and with the person who
sponsored you.

You have restricted (not login!) ssh access to the system so if at some
point you wish to update your ssh key, you can do so with the following
command:

    ssh sourceware.org appendkey < publickeyfile

This will append 'publickeyfile' (usually ~/.ssh/id_dsa.pub or
~/.ssh/id_rsa.pub) to your existing allowed ssh keys. If you have entirely
lost your old ssh key, then grovel to overseers@sourceware.org and someone
may take pity on you. If you suspect your key has been compromised,
let the overseers know as soon as possible.

You can also update your email forwarding with the command:

    ssh sourceware.org email your@newmail.com

If you have questions, please do not reply to this email.  Ask your
project mailing list.

       reply	other threads:[~2012-09-12 23:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120321204838.18781.qmail@sourceware.org>
2012-09-12 23:30 ` Siva Chandra [this message]
2012-09-13  4:07   ` Ian Lance Taylor
2012-09-13 21:35     ` Siva Chandra
2012-09-14  4:42       ` Ian Lance Taylor
2012-09-20  9:54         ` Siva Chandra
2012-09-20 11:08           ` Frank Ch. Eigler
2012-09-20 19:57             ` Siva Chandra
     [not found] <20200310183342.35494395A062@sourceware.org>
2022-07-27 20:23 ` Vineet Gupta
2022-07-27 20:35   ` Frank Ch. Eigler
2022-07-27 21:36     ` Vineet Gupta
2022-07-27 21:57       ` Frank Ch. Eigler
2022-07-28  0:38         ` Vineet Gupta
2022-07-28  0:41           ` Frank Ch. Eigler
2022-07-28  0:45             ` Vineet Gupta

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='CAGyQ6gx46ZBagb5rxzoncvdBEMKn1YfDxQSb=MVfkE9X-5fOLA@mail.gmail.com' \
    --to=sivachandra@google.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).