From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Abel Vesa <abel.vesa@linaro.org>
Cc: keys@linux.kernel.org
Subject: Re: abel.vesa@linaro.org
Date: Wed, 1 Nov 2023 12:30:20 -0400 [thread overview]
Message-ID: <20231101-purring-unyielding-moose-cd2eee@meerkat> (raw)
In-Reply-To: <ZUJt2EMUuyhZC2sM@linaro.org>
On Wed, Nov 01, 2023 at 05:25:12PM +0200, Abel Vesa wrote:
> -----BEGIN PGP PUBLIC KEY BLOCK-----
Updated, thanks. Your ssh key has also been updated to use your newest Auth
subkey.
-K
prev parent reply other threads:[~2023-11-01 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 15:25 abel.vesa@linaro.org Abel Vesa
2023-11-01 16:30 ` 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=20231101-purring-unyielding-moose-cd2eee@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=abel.vesa@linaro.org \
--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).