From: "Christoph Müllner" <cmuellner@linux.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Overseers mailing list <overseers@sourceware.org>,
Jim Wilson <jimw@sifive.com>
Subject: Re: Request from Christoph Müllner
Date: Fri, 26 Feb 2021 00:45:42 +0100 [thread overview]
Message-ID: <CAHB2gtSE3HROm2sBJN3svJF6S1rsXnPFXW08D_bfR2qTp3DuPw@mail.gmail.com> (raw)
In-Reply-To: <20210225234211.GD15883@redhat.com>
On Fri, Feb 26, 2021 at 12:42 AM Frank Ch. Eigler <fche@redhat.com> wrote:
> Hi -
>
> > I can confirm, that I have a proper (but old) SSH RSA key for the
> cmuellner
> > account. So please ignore my request for creating the new user "cm".
>
> OK.
>
> > Additionally, I have just uploaded an additional SSH EC key using
> > cat ~/.ssh/id_ed25519.pub | ssh cmuellner@gcc.gnu.org appendkey
> > What is the best way to delete the old SSH RSA key?
>
> It looks gone already, don't worry about it.
>
> > I also tried to update my email-forwarding, but it failed like this:
> > echo "cmuellner@linux.com" | ssh cmuellner@gcc.gnu.org
> email-forwarding
> > error encountered - invalid email format
> > Could you please tell me how to do this properly?
>
> https://sourceware.org/sourceware/accountinfo.html
>
> ... gives the necessary runes.
>
Thanks for the pointer!
Christoph
next prev parent reply other threads:[~2021-02-25 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 21:35 cmuellner
2021-02-25 22:11 ` Jim Wilson
2021-02-25 23:35 ` Christoph Müllner
2021-02-25 23:42 ` Frank Ch. Eigler
2021-02-25 23:45 ` Christoph Müllner [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-24 13:18 Request from Christoph M?llner christoph.muellner
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=CAHB2gtSE3HROm2sBJN3svJF6S1rsXnPFXW08D_bfR2qTp3DuPw@mail.gmail.com \
--to=cmuellner@linux.com \
--cc=fche@redhat.com \
--cc=jimw@sifive.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).