From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: keys@linux.kernel.org
Subject: Re: New key
Date: Tue, 9 May 2023 14:49:04 -0400 [thread overview]
Message-ID: <20230509-raisin-escort-obeys-9bb656@meerkat> (raw)
In-Reply-To: <37981d82-c7e7-3c06-ab21-47f2c78ef143@linaro.org>
On Tue, May 09, 2023 at 11:51:24AM +0200, Konrad Dybcio wrote:
> Hi,
>
> please import my key. This time it's got signatures on it :P
Added, thanks!
-K
next prev parent reply other threads:[~2023-05-09 18:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 9:51 New key Konrad Dybcio
2023-05-09 18:49 ` Konstantin Ryabitsev [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-14 15:30 Konrad Dybcio
2023-04-17 16:35 ` Konstantin Ryabitsev
2023-02-09 10:53 David Gibson
2023-02-09 20:41 ` Konstantin Ryabitsev
2023-02-10 0:06 ` David Gibson
[not found] ` <Y+mh9AALS6uCC/0A@yekko>
2023-02-21 22:28 ` Konstantin Ryabitsev
2023-02-22 3:42 ` David Gibson
2023-02-23 16:19 ` Konstantin Ryabitsev
2023-02-24 4:05 ` David Gibson
2023-02-24 4:21 ` David Gibson
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=20230509-raisin-escort-obeys-9bb656@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=keys@linux.kernel.org \
--cc=konrad.dybcio@linaro.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 NNTP newsgroup(s).