Hi > This does mean that any patches to the main haddock repo need to pass > validate.
I contribute patches to Haddock, but have no way to run validate (I don't have my own computer currently, and can't install mingw/cygwin on any of the machines I have access to). What should I do? I doubt the patches I supply will break validate, as they all concern the Hoogle back end, but I have no real way of knowing that without actually running validate. Perhaps one solution would be to pull from haddock only up until the most recent tag (if darcs supports a feature). Then everyone can work on the main haddock repo, and "push" the changes into GHC by simply tagging, after validation. Thanks Neil _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
