From: Stan Shebs <stanshebs@google.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: Replacement RSA key
Date: Fri, 25 Jun 2021 14:41:05 -0400 [thread overview]
Message-ID: <CA+5-Q5KVeKOefYRsZ+DNH_ii4DmjSN2v4oKpJUn8utdoM7JdDQ@mail.gmail.com> (raw)
In-Reply-To: <YNYhZgkDu+wWzkYm@elastic.org>
Works perfectly now, thanks!
On Fri, Jun 25, 2021 at 2:33 PM Frank Ch. Eigler <fche@elastic.org> wrote:
> Hi -
>
> > Hi, did this get overlooked?
>
> Yes, but no longer. Try now. :-)
>
> - FChE
>
prev parent reply other threads:[~2021-06-25 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 21:19 Stan Shebs
2021-06-25 18:26 ` Stan Shebs
2021-06-25 18:33 ` Frank Ch. Eigler
2021-06-25 18:41 ` Stan Shebs [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=CA+5-Q5KVeKOefYRsZ+DNH_ii4DmjSN2v4oKpJUn8utdoM7JdDQ@mail.gmail.com \
--to=stanshebs@google.com \
--cc=fche@elastic.org \
--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).