From: Jie Zhang <jzhang918@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: overseers@sourceware.org
Subject: Re: public key
Date: Tue, 16 Apr 2024 11:04:08 -0400 [thread overview]
Message-ID: <CACYR8yON-cshQNSmEWJhWLSmyJ=5dACVy-2UbG_MAo2xpMQKWA@mail.gmail.com> (raw)
In-Reply-To: <2cefa3d4-f83b-4da2-b464-a4210e96cbdb@dronecode.org.uk>
Hi Jon,
Sorry for sending emails to you privately.
On Tue, Apr 16, 2024 at 9:18 AM Jon Turney <jon.turney@dronecode.org.uk> wrote:
>
> On 16/04/2024 14:12, Jie Zhang wrote:
> > Please reply
> >
> > On Thu, Apr 11, 2024 at 3:01 PM Jie Zhang <jzhang918@gmail.com> wrote:
> >
> >> Hi Jon,
> >>
> >> 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.
>
I googled and found this
https://cygwin.com/pipermail/cygwin-apps/2023-November/043296.html
and this
https://cygwin.com/pipermail/cygwin-apps/2024-January/043419.html
I thought maybe cygwin-apps might be the mailing list I should send my
new public key, but the mailing list name looks not for this purpose.
That's why I asked privately to make sure this is the right way to
update my key.
> 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
>
> [1] https://www.sourceware.org/sourceware/accountinfo.html
>
Thank you, I will try.
Jie
prev parent reply other threads:[~2024-04-16 15:04 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
2024-04-19 3:35 ` Jie Zhang
2024-04-16 15:04 ` Jie Zhang [this message]
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='CACYR8yON-cshQNSmEWJhWLSmyJ=5dACVy-2UbG_MAo2xpMQKWA@mail.gmail.com' \
--to=jzhang918@gmail.com \
--cc=jon.turney@dronecode.org.uk \
--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).