[Qa-jenkins-scm] [jenkins.debian.net] 01/01: reproducible: add link to our toolchain description in the wiki

[Holger Levsen]

This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch master
in repository jenkins.debian.net.

commit b23181b28e8b3b047e1d921fa4ebd326f1307ee2
Author: Holger Levsen <holger at layer-acht.org>
Date:   Mon Mar 16 01:10:25 2015 +0100

    reproducible: add link to our toolchain description in the wiki
---
 README | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README b/README
index ad37f2a..9c2773c 100644
--- a/README
+++ b/README
@@ -125,7 +125,7 @@ Installation tests inside chroot environments.
 
 * The (current) purpose of https://reproducible.debian.net is to show the prospects of reproducible builds for Debian. IOW: this is research, showing what could (and should) be done... check https://wiki.debian.org/ReproducibleBuilds for the real status of the project!
 
-* Currently, three suites are tested on amd64: 'testing', 'unstable' and 'experimental'. The tests are done using 'pbuilder' through four builder jobs, alpha, beta, gamma and delta, which are each constantly testing packages and saving the results of these tests.
+* Currently, three suites are tested on amd64: 'testing', 'unstable' and 'experimental'. The tests are done using 'pbuilder' using link:https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain[our toolchain] through four builder jobs, alpha, beta, gamma and delta, which are each constantly testing packages and saving the results of these tests.
 
 * The jenkins job overview at https://jenkins.debian.net/view/reproducible/ probably makes it clearer how the job scheduling works in practice.
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/qa/jenkins.debian.net.git