Mailing list CCs (Was: Confused about the sub-modules)

Hi Erik, Am Mittwoch, den 21.12.2016, 20:13 +1100 schrieb Erik de Castro Lopo: > (No need to CC me, I'm subscribed to ghc-devs). I see where you are coming from, I also joined the Haskell community after having been socialized on Debian mailing lists. Slightly unfortunately, unsolicited CCs are

Re: Confused about the sub-modules

I *just* pushed a Cabal submodule update, so Erik probably hadn't gotten it. Excerpts from Ben Gamari's message of 2016-12-21 14:14:37 -0500: > Erik de Castro Lopo writes: > > > Edward Z. Yang wrote: > > > >> Not any more. The commit just has to exist in the remote repo

Re: Confused about the sub-modules

Erik de Castro Lopo writes: > Edward Z. Yang wrote: > >> Not any more. The commit just has to exist in the remote repo (that's >> what the lint checks.) > > So this is where I am running into trouble. Everything for process > and directory is fine, but for Cabal and

Re: Confused about the sub-modules

Edward Z. Yang wrote: > Not any more. The commit just has to exist in the remote repo (that's > what the lint checks.) So this is where I am running into trouble. Everything for process and directory is fine, but for Cabal and containers, the git repo on git.haskell.org is missing the commits I

RE: Confused about the sub-modules

Castro Lopo <mle...@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 eve

Re: Confused about the sub-modules

Not any more. The commit just has to exist in the remote repo (that's what the lint checks.) Excerpts from Alan & Kim Zimmerman's message of 2016-12-21 09:20:15 +0200: > For the utils/haddock submodule there is a ghc-head branch, and the commit > should be on that before pushing to GHC master

Re: Confused about the sub-modules

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

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

Confused about the sub-modules

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