I saw that a considerable number of people forked GHC on GitHub. I am wondering, does that make any sense without forking all the package repos as well?
In my experience of hacking GHC, once you go off onto a major branch, at least core packages, such as base, will diverge pretty quickly as well. And you usually need to keep the testsuite in sync with your GHC tree as well unless you want to manually keep track of spurious failures due to divergence of the repos. So, how are you guys handling this? Would the use of submodules, instead of separate repos and the sync-all script, address that problem, so that forking the main repo would also fork the submodules? Manuel _______________________________________________ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listinfo/cvs-ghc
