From 76ab2eab312371294e1a2f550504f3a9d5cef3b1 Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Fri, 21 May 2021 19:07:35 +0200 Subject: manuals: document hash equivalence (From yocto-docs rev: 7fad0873207980a747f79b2ce29ec0dc6c6c3cdf) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie --- documentation/test-manual/reproducible-builds.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'documentation/test-manual') diff --git a/documentation/test-manual/reproducible-builds.rst b/documentation/test-manual/reproducible-builds.rst index 349cd1953e..5977366c9e 100644 --- a/documentation/test-manual/reproducible-builds.rst +++ b/documentation/test-manual/reproducible-builds.rst @@ -33,10 +33,10 @@ need to rebuild to add a security fix. If this happens, only the components that have been modified should change at the binary level. This would lead to much easier and clearer bounds on where validation is needed. -This also gives an additional benefit to the project builds themselves, our hash -equivalence for :ref:`Shared State ` -object reuse works much more effectively when the binary output remains the -same. +This also gives an additional benefit to the project builds themselves, our +:ref:`overview-manual/concepts:Hash Equivalence` for +:ref:`overview-manual/concepts:Shared State` object reuse works much more +effectively when the binary output remains the same. .. note:: -- cgit v1.2.3-54-g00ecf