Info here. I hope it is up to date https://ghc.haskell.org/trac/ghc/wiki/Repositories If it's out of date, please fix! Simon | -----Original Message----- | From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of Edward Z. | Yang | Sent: 21 December 2016 06:49 | To: Erik de Castro Lopo <mle+hs@mega-nerd.com> | Cc: ghc-devs <ghc-devs@haskell.org> | Subject: Re: Confused about the sub-modules | | Once the commit is upstream, I just checkout a newer commit from master and | then commit it as a submodule update. Maybe it's wrong but no one has ever | told me otherwise. Around release time the release manager makes sure all | the libraries correspond to actual releases. | | Edward | | Excerpts from Erik de Castro Lopo's message of 2016-12-21 17:33:36 +1100: | > Hi all, | > | > I'm a bit confused about how the GHC dev tree handles submodules like | > libraries/Cabal, libraries/process, libraries/directory and | > libraries/containers. | > | > All of these libraries/submodules seem to have their own github | > projects where people can submit PRs, but once the commits have been | > made there, what is the process to get submodules updated in the GHC tree? | > | > Any light people can shed on this process would be appreciated. | > | > Erik | _______________________________________________ | ghc-devs mailing list | ghc-devs@haskell.org | https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.haskell | .org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc- | devs&data=02%7C01%7Csimonpj%40microsoft.com%7C60ddf19e8b144b4508c608d4296d71 | ea%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636178997417986784&sdata=D3t | 262ge8xaOYdKm%2Byqx7oCIaHs6mTtY0g17zGU54Pw%3D&reserved=0