public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Peter Bergner via Overseers <overseers@sourceware.org>
Cc: Peter Bergner <bergner@linux.ibm.com>,
	jeevitha <jeevitha@linux.vnet.ibm.com>
Subject: Re: Add SSH key
Date: Tue, 29 Aug 2023 22:18:52 +0200	[thread overview]
Message-ID: <20230829201852.GA26251@gnu.wildebeest.org> (raw)
In-Reply-To: <66bda870-136b-78e8-f97e-59304c9fe070@linux.ibm.com>

Hi Peter, Hi Jeevitha,

On Tue, Aug 29, 2023 at 02:55:45PM -0500, Peter Bergner via Overseers wrote:
> On 8/29/23 2:43 PM, Mark Wielaard wrote:
> > On Tue, Aug 29, 2023 at 07:46:59PM +0530, jeevitha via Overseers wrote:
> >> I lost my SSH key which is associated with my GCC
> >> account(jeevitha@gcc.gnu.org) due to some disk failure on my
> >> machine. I have created new keys attaching here. Please help me by
> >> adding this key to my account.
> > 
> > Note that we now have a private admin-requests@sourceware.org to handle
> > account issues. So you don't have to use the public list.
> > 
> > Also can we get your original approver (CCed) or another GCC
> > maintainer to ack your request to make sure it is you?
> 
> I can confirm Jeevitha lost her ssh keys and needs a new set installed.

Thanks for confirming. All should be setup now with the new key.

In you want to test things before committing, please see
https://sourceware.org/sourceware/accountinfo.html

Cheers,

Mark

  reply	other threads:[~2023-08-29 20:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 14:16 jeevitha
2023-08-29 19:43 ` Mark Wielaard
2023-08-29 19:55   ` Peter Bergner
2023-08-29 20:18     ` Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-02 12:59 Add SSH Key David Ayers
2005-07-02 16:04 ` Ian Lance Taylor
2005-07-02 22:23 ` Gerald Pfeifer
2005-07-03  4:03   ` David Ayers

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=20230829201852.GA26251@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=bergner@linux.ibm.com \
    --cc=jeevitha@linux.vnet.ibm.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).