From: Nicolas Schier <nicolas@fjasle.eu>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Jonathan Corbet <corbet@lwn.net>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org,
ab@php.net
Subject: Re: [PATCH] Documentation: kbuild: Add document about reproducible builds
Date: Fri, 13 Sep 2019 08:28:11 +0200 [thread overview]
Message-ID: <20190913062811.GG8267@fjasle.eu> (raw)
In-Reply-To: <20190911115353.yngbk6hf6gwctock@decadent.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
Hi Ben,
thanks for that document, I really enjoyed reading it!
On Wed, Sep 11, 2019 at 12:53:53PM +0100, Ben Hutchings wrote:
[...]
> diff --git a/Documentation/kbuild/reproducible-builds.rst b/Documentation/kbuild/reproducible-builds.rst
> new file mode 100644
> index 000000000000..4d988faf93b8
> --- /dev/null
> +++ b/Documentation/kbuild/reproducible-builds.rst
> @@ -0,0 +1,115 @@
> +===================
> +Reproducible builds
> +===================
> +
> +It is generally desirable that the building the same source code with
In this sentence, I think there is either one word to much (the first
'the') or some word is missing (e.h. 'of').
Kind regards,
Nicolas
> +the same set of tools is reproducible, i.e. the output is always
> +exactly the same. This makes it possible to verify that the build
> +infrastructure for a binary distribution or embedded system has not
> +been subverted. This can also make it easier to verify that a source
> +or tool change does not make any difference to the resulting binaries.
--
epost: nicolas@fjasle.eu irc://oftc.net/nsc
↳ gpg: 18ed 52db e34f 860e e9fb c82b 7d97 0932 55a0 ce7f
-- frykten for herren er opphav til kunnskap --
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-09-13 6:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 11:53 [PATCH] Documentation: kbuild: Add document about reproducible builds Ben Hutchings
2019-09-11 12:17 ` Masahiro Yamada
2019-09-11 13:04 ` Ben Hutchings
2019-09-11 13:14 ` Ben Hutchings
2019-09-12 1:47 ` Masahiro Yamada
2019-09-13 6:28 ` Nicolas Schier [this message]
2019-09-14 11:15 ` Ben Hutchings
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=20190913062811.GG8267@fjasle.eu \
--to=nicolas@fjasle.eu \
--cc=ab@php.net \
--cc=ben@decadent.org.uk \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=yamada.masahiro@socionext.com \
/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