public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Vineet Gupta <vineet.gupta@linux.dev>
To: overseers@sourceware.org
Subject: Fwd: Welcome to sourceware.org
Date: Wed, 27 Jul 2022 13:23:59 -0700	[thread overview]
Message-ID: <bf4a8ff7-161a-9ec8-51e2-47f995353fbf@linux.dev> (raw)
In-Reply-To: <20200310183342.35494395A062@sourceware.org>

Hi,

Looks like in my job transition I lost my personal ssh key and can't 
update my email address for my sourceware account.
Could you please help !

Thx,
-Vineet


-------- Forwarded Message --------
Subject: 	Welcome to sourceware.org
Date: 	Tue, 10 Mar 2020 18:33:42 +0000
From: 	root <root@sourceware.org>
To: 	vgupta@sourceware.org
CC: 	carlos@redhat.com



Your account on sourceware.org is now active. The login name is
"vgupta". Mail sent to that address is forwarded to
vgupta@synopsys.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:[~2022-07-27 20:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200310183342.35494395A062@sourceware.org>
2022-07-27 20:23 ` Vineet Gupta [this message]
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
     [not found]   ` <05e065ac-eb5c-2c08-1947-0f1c75940031@linux.dev>
2022-11-29 10:19     ` Fwd: " Mark Wielaard
2022-11-29 19:55       ` Vineet Gupta
2022-11-29 21:49         ` Mark Wielaard
     [not found] <20120321204838.18781.qmail@sourceware.org>
2012-09-12 23:30 ` Siva Chandra
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

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=bf4a8ff7-161a-9ec8-51e2-47f995353fbf@linux.dev \
    --to=vineet.gupta@linux.dev \
    --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).