From: "Frank Ch. Eigler" <fche@elastic.org>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: overseers@sourceware.org
Subject: Re: Remove my keys?
Date: Mon, 13 Jan 2020 20:33:00 -0000 [thread overview]
Message-ID: <20200113203311.GI89021@elastic.org> (raw)
In-Reply-To: <CABu31nMpQ8G=yKtTbrB3NXXSXARJzovtff8zbCfhz=tA1sLDzg@mail.gmail.com>
Hi -
> I used to contribute to GCC but I haven't committed anything in years.
> I also haven't updated my keys. Can they please be remove from
> sourceware? Seems safer than keeping them there, inactive...
Only public keys are on sourceware.org, and in your case, only a .pub
that sourceware itself no longer accepts for logins (old DSA). I will
still nuke it, but there was no risk.
- FChE
prev parent reply other threads:[~2020-01-13 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 20:30 Steven Bosscher
2020-01-13 20:33 ` Frank Ch. Eigler [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=20200113203311.GI89021@elastic.org \
--to=fche@elastic.org \
--cc=overseers@sourceware.org \
--cc=stevenb.gcc@gmail.com \
/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).