From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: keys@linux.kernel.org
Subject: Re: joseph.salisbury@canonical.com
Date: Tue, 1 Mar 2022 10:02:46 -0500 [thread overview]
Message-ID: <20220301150246.wseghjaaenync4kl@meerkat.local> (raw)
In-Reply-To: <8c4459a3-9dac-0c35-a4a6-0cc219081b05@canonical.com>
On Mon, Feb 28, 2022 at 08:41:49PM -0500, Joseph Salisbury wrote:
Added 6CEF3D27CA5B141E, thanks.
-K
prev parent reply other threads:[~2022-03-01 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 1:41 joseph.salisbury@canonical.com Joseph Salisbury
2022-03-01 15:02 ` Konstantin Ryabitsev [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=20220301150246.wseghjaaenync4kl@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=joseph.salisbury@canonical.com \
--cc=keys@linux.kernel.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).