public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Vineet Gupta <vineet.gupta@linux.dev>
To: "Frank Ch. Eigler" <fche@elastic.org>,
	Overseers mailing list <overseers@sourceware.org>
Subject: Re: Fwd: Welcome to sourceware.org
Date: Wed, 27 Jul 2022 14:36:23 -0700	[thread overview]
Message-ID: <a4dfe34a-8fcb-426b-7278-6433435091f6@linux.dev> (raw)
In-Reply-To: <YuGhliK2SGln8zrE@elastic.org>

[-- Attachment #1: Type: text/plain, Size: 265 bytes --]

Hi,

On 7/27/22 13:35, Frank Ch. Eigler wrote:
> 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 !
> Please send a new ssh public key.

PFA !

Thx,
-Vineet

[-- Attachment #2: id_rsa.pub --]
[-- Type: application/vnd.ms-publisher, Size: 579 bytes --]

  reply	other threads:[~2022-07-27 21:36 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
2022-07-27 20:35   ` Frank Ch. Eigler
2022-07-27 21:36     ` Vineet Gupta [this message]
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=a4dfe34a-8fcb-426b-7278-6433435091f6@linux.dev \
    --to=vineet.gupta@linux.dev \
    --cc=fche@elastic.org \
    --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).