On Wed, Aug 17, 2011 at 11:10:09AM +0000, Simon Peyton-Jones wrote:
> 
> Consider the 'containers' line of the table at the bottom.  We can't figure 
> out why we need the mirror 
> http://darcs.haskell.org/git-mirrors/containers/.git/.   Would it not be an 
> easier workflow to 
>   - pull from the containers master repo      
> git://github.com/haskell/containers.git
>   - validate
>   - push to the GHC lagging repo 
> http://darcs.haskell.org/packages/containers.git/
> ?

The
    http://darcs.haskell.org/packages/containers.git/
repo has a hook that checks that the patches being pushed are already in
    http://darcs.haskell.org/git-mirrors/containers/.git/
so that we can't forget to send changes upstream. I don't think we can
do that without a local mirror.

> Also, in the picture, what does "local git upstream" mean?  Should it not say 
> "git upstream"?

Yes, thanks; fixed.


Thanks
Ian


_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to