For the utils/haddock submodule there is a ghc-head branch, and the commit should be on that before pushing to GHC master with a submodule update.
I do not know if that convention is followed on any of the other libraries. Alan On Wed, Dec 21, 2016 at 8:48 AM, Edward Z. Yang <[email protected]> wrote: > 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 > [email protected] > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs >
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
