From: Tanvir Roshid <tanvir.roshid@codethink.co.uk>
To: keyrings@vger.kernel.org
Subject: keyutils - reproducibility
Date: Thu, 15 Jun 2023 14:46:12 +0100 [thread overview]
Message-ID: <8b9eed97-b41c-34e3-8183-056f8e5643b5@codethink.co.uk> (raw)
Hi,
I hope you are well.
I made a post here:
https://github.com/auristor/keyutils/issues/1#issue-1750897652 and was
advised to directly contact.
What is the best way to ensure that the buildid is reproducible? The
current patch is not a proper solution.
Kind regards,
Tanvir
reply other threads:[~2023-06-15 14:04 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=8b9eed97-b41c-34e3-8183-056f8e5643b5@codethink.co.uk \
--to=tanvir.roshid@codethink.co.uk \
--cc=keyrings@vger.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).