Travis validation on a GHC fork?

Richard Eisenberg eir at
Thu Nov 13 17:38:45 UTC 2014

I don't think this answer "scales" -- what if I've forked some submodules but not others? I think it should perhaps check to see if there is a forked submodule, and then go to GHC's if there isn't.

I suppose I could implement this myself, but I'm confident there is someone who could do it in roughly a quarter of the time this would take me...


On Nov 12, 2014, at 5:19 PM, Joachim Breitner <mail at> wrote:

> Hi,
> Am Mittwoch, den 12.11.2014, 13:24 -0500 schrieb Richard Eisenberg:
>> Hi Joachim,
>> I just tried to use Travis for validation on my fork of GHC, to avoid
>> sending out emails associated with a wip/... commit. But, Travis
>> couldn't find the submodules. Here's the tail of my log:
>> [..]
>> I could probably figure out the right commands to fix this, but then
>> my local .travis.yml would be different than the proper one, and that
>> can cause various headaches down the road.
> we could change the official .travis.yml file to rewrite the urls to
> point to I don’t know of any more elegant solution, but
> maybe our submodule experts know something?
> Greetings
> Joachim
> -- 
> Joachim “nomeata” Breitner
>  mail at joachim-breitner.de
>  Jabber: nomeata at  • GPG-Key: 0xF0FBF51F
>  Debian Developer: nomeata at
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at

More information about the ghc-devs mailing list