public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Jon Turney via Overseers <overseers@sourceware.org>
Cc: Jie Zhang <jzhang918@gmail.com>,
	Jon Turney <jon.turney@dronecode.org.uk>
Subject: Re: public key
Date: Tue, 16 Apr 2024 15:28:07 +0200	[thread overview]
Message-ID: <20240416132807.GA25080@gnu.wildebeest.org> (raw)
In-Reply-To: <2cefa3d4-f83b-4da2-b464-a4210e96cbdb@dronecode.org.uk>

Hi,

On Tue, Apr 16, 2024 at 02:18:15PM +0100, Jon Turney via Overseers wrote:
> On 16/04/2024 14:12, Jie Zhang wrote:
> >On Thu, Apr 11, 2024 at 3:01 PM Jie Zhang <jzhang918@gmail.com> wrote:
> >
> >>I need to update my public key to ED25519 for git ssh access on
> >>sourceware.org. Is it correct for me to send the new public key to
> >>cygwin-apps@sourceware.org ?
> 
> No.
> 
> I don't know what could have lead you to believe that personally
> contacting me is the way to resolve this, but I'd be obliged if you
> could point out the source of this disinformation so I can get it
> corrected.
> 
> If you still have an old key, you can add a new key using the
> self-service methods described at [1]
> 
> Otherwise, ask on overseers@sourceware.org

Note that overseers is a public list. There is also
admin-requests@sourceware.org which is a private list where you can
ask questions about your account.

See also https://sourceware.org/mission.html#organization for other
ways to contact the different sourceware admins.

> [1] https://www.sourceware.org/sourceware/accountinfo.html

Cheers,

Mark

  reply	other threads:[~2024-04-16 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACYR8yPu_3bjg8Skb01jkbYCG04a=nE8qNPV0EPZsNEhn-x6Bg@mail.gmail.com>
     [not found] ` <CACYR8yMjw_kDWMgMdWOnC0JL1vx5XxgUcT7uZUiKoJg=HtMvKA@mail.gmail.com>
2024-04-16 13:18   ` Jon Turney
2024-04-16 13:28     ` Mark Wielaard [this message]
2024-04-19  3:35       ` Jie Zhang
2024-04-16 15:04     ` Jie Zhang

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=20240416132807.GA25080@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=jon.turney@dronecode.org.uk \
    --cc=jzhang918@gmail.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).