Hi,

Am Samstag, den 08.11.2014, 22:33 -0500 schrieb Richard Eisenberg:
> I've stopped validating locally, allowing Travis to do it for me. If
> you use a `wip/...` branch and push to the main GHC repo, you can find
> build reports at travis-ci.org/ghc/ghc. Or, I'm sure if you clue
> Travis in, this can also work if you push to your own GitHub fork of
> GHC.

of course this spams ghc-commits quite a lot. So while I think it’s
reasonable to use this method to validate something that you expect to
pass, I would advice using your own GitHub fork if you do trial and
error. It’s just takes a few clicks or so to set it up, including
enabling Travis.

Greetings,
Joachim


-- 
Joachim “nomeata” Breitner
  m...@joachim-breitner.de • http://www.joachim-breitner.de/
  Jabber: nome...@joachim-breitner.de  • GPG-Key: 0xF0FBF51F
  Debian Developer: nome...@debian.org

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Reply via email to