From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: signatures@kernel.org
Subject: Patch-Id:
Date: Mon, 10 Feb 2020 19:16:54 -0500 [thread overview]
Message-ID: <attestation-git-foo-bar@foo-bar.local> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Message-Id: git-foo-bar@foo-bar.local
Patch-Id:
Info-SHA256: 067496314cb7a69b2827e050666d39531499b7e5120d3c5a48f756d3bd9e5306
Message-SHA256: e07474d8ab2d6c23c8d7c84877012f7cf429a70764021fe12923185fff660efd
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQR2vl2yUnHhSB5njDW2xBzjVmSZbAUCXkHyhAAKCRC2xBzjVmSZ
bLpVAP9xRsMZqeoX4WiDWIkiouJ6X7yYSyysA/9iMgCcUbxTQQD/fdd+bfm6YzNf
D2bdz9OPE1tmmaWyZ/v75suAeNA+egs=
=RbLX
-----END PGP SIGNATURE-----
reply other threads:[~2020-02-11 0:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=attestation-git-foo-bar@foo-bar.local \
--to=konstantin@linuxfoundation.org \
--cc=signatures@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.