andrey.mokhov at newcastle.ac.uk
Fri Oct 20 11:36:37 UTC 2017
Hi Moritz and Herbert,
Thank you for detailed comments! We clearly need to carefully think through our options for merging Hadrian.
Can I invite you both and everyone else to continue the discussion in https://github.com/snowleopard/hadrian/issues/440? Long email threads tend to become hard to read/follow and get lost.
In my view, the two most important requirements in the long term are:
1) Preserving the commit/issue/pull-request history. A GHC developer fighting a strange build failure should be able to find a relevant discussion not only now but in 5 years from now. This may be solved via documentation, i.e. gradually moving all discussions from GitHub to docs/comments. That's a lot of hard work.
2) Making it convenient for GHC developers to work on Hadrian. To me, git submodules are not convenient at all, but maybe there is just no other option given the requirement (1). Is git subtree a solution?
More information about the ghc-devs