Relocating (some of) GHC's core-libraries to

Edward Kmett ekmett at
Tue Apr 29 14:46:45 UTC 2014

I would really like that as well.

My experience is it is rather easy to get users to put together a pull
request through github.

It is rather more like pulling teeth to get them to use git properly and
put together a traditional patch.

This would greatly open up the workflow for end users contributing things
like small documentation fixes and the like.


On Tue, Apr 29, 2014 at 5:58 AM, Herbert Valerio Riedel
<hvriedel at>wrote:

> Hello Simon,
> On 2014-04-28 at 11:28:35 +0200, Simon Marlow wrote:
> [...]
> >> However, we can configure the lagged mirror such that we'd automatically
> >> mirror github's 'master' branch into our lagged mirror (we'd still be
> >> free to create local wip/* or ghc-7.10 branches at if
> >> needed)
> >
> > I think that's fine.  As Simon points out, we already have lagging
> > repo functionality in the form of the submodule links, so the repo on
> > can be a pure mirror.
> Just so I get this right, does "pure mirror" here mean that we don't
> want users to be able to push to the automatically mirrored repo on
> at all, but rather the only way to get any commits into
> the mirrored repo would be push it via the GitHub repo?
> (I'd like that, as it would make the set-up easier and hopefully less
> confusing, as there'd be only a single data-flow path)
> Cheers,
>   hvr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the ghc-devs mailing list