bit rotting of Haddock

2012-08-27 Thread Simon Hengel
Hi, we have several issues on Haddock's ghc-7.6 branch. I fixed some of those, but some still persist. Isolated, none of those issues are a big deal. But combined they are. Is there a way we can prevent situations like this in the future? Would it work to establish the convention that if you ch

[nightly] 27-Aug-2012 build of HEAD on i386-unknown-linux (cam-02-unx)

2012-08-27 Thread GHC Build Reports
Build description = HEAD on i386-unknown-linux (cam-02-unx) Build location= /playpen/simonmar/nightly/HEAD Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx Nightly build started on cam-02-unx at Mon Aug 27 18:00:01 BST 2012. checking out new source tree

[nightly] 27-Aug-2012 build of STABLE on i386-unknown-linux (cam-02-unx)

2012-08-27 Thread GHC Build Reports
Build description = STABLE on i386-unknown-linux (cam-02-unx) Build location= /playpen/simonmar/nightly/STABLE Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-02-unx Nightly build started on cam-02-unx at Mon Aug 27 18:10:01 BST 2012. checking out new source tree

[nightly] 27-Aug-2012 build of HEAD on x86_64-unknown-linux (cam-04-unx)

2012-08-27 Thread GHC Build Reports
Build description = HEAD on x86_64-unknown-linux (cam-04-unx) Build location= /64playpen/simonmar/nightly/HEAD-cam-04-unx Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-04-unx Nightly build started on cam-04-unx at Mon Aug 27 18:00:01 BST 2012. checking out new source

[nightly] 27-Aug-2012 build of STABLE on x86_64-unknown-linux (cam-04-unx)

2012-08-27 Thread GHC Build Reports
Build description = STABLE on x86_64-unknown-linux (cam-04-unx) Build location= /64playpen/simonmar/nightly/STABLE-cam-04-unx Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-04-unx Nightly build started on cam-04-unx at Mon Aug 27 18:10:01 BST 2012. checking out new s