If the status quo is poor, then why not merge the two? git-subtree won't fix the problem and will arguably be even harder to manage than submodules.

Best,

On Wed, 6 Mar 2019 at 15:59, Ben Gamari <ben@smart-cactus.org> wrote:
Sylvain Henry <sylvain@haskus.fr> writes:

> Why don't we just put Haddock into GHC's repository? It was proposed in
> a previous discussion in February [1] and it would avoid the bad
> experience of having it as a submodule while keeping it in sync.
>
I'm reluctant to keep it in the GHC tree; it really is a separate
project with separate maintainership, dependencies, and contributors.

That being said, I do agree that the status quo is pretty poor. I was
going to suggest managing it with git-subtree instead, but I'm not sure
this would be much of an improvement.

Cheers,

 - Ben
_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs