How do I build GHC 7.6 from source?

[Claus Reinke]

> Well, it doesn't quite have the same drawbacks as submodules, because our solution places a burden 
> only on someone who wants to recover a particular repository state, rather than on everyone doing 
> development.
>
> I think it's worth keeping an eye on submodules in case they fix the gotchas in the UI, but at the 
> moment it looks like we'd have a lot of confused developers, lost work and accidental breakages 
> due to people not understanding how submodules work or forgetting to jump through the correct 
> hoops.
>
> I'm not saying fingerprints are a good solution, obviously they only solve a part of the problem, 
> but the current tooling for submodules leaves a lot to be desired.

Since you already have fingerprinting in place, have you looked
into 'git subtree' for the remaining functionality? Used to be an
addon module, has recently been merged into git (contrib/).

http://apenwarr.ca/log/?m=200904#02

https://github.com/gitster/git/blob/634392b26275fe5436c0ea131bc89b46476aa4ae/contrib/subtree/git-subtree.txt

https://github.com/apenwarr/git-subtree

I don't have further information or recommendations, just wanted
to pass on this alternative - it tends to come up when googling for
'git submodule' issues, and most reports on it have been favorable
(no idea whether it would work for the size and complexity of the
ghc&friends repo landscape).

Claus