A pretty bare version is now up and linked from the Repositories page (http://hackage.haskell.org/trac/ghc/wiki/GitHubGHC). I'm not fully clear how much detail is necessary, nor how much duplication of content should exist on the page. Much of what could be included exists elsewhere on the GHC wiki or in the Github docs. For instance, should I add instructions for setting up SSH keys with Github? Should I make provisions for the proper dev workflow? Ought I to explain the patch submission process?
Jack On Jul 13, 2011, at 5:33 PM, Karel Gardas wrote: > > I've just put as simple as possible paragraph about getting GHC sources from > GitHub.com on > http://hackage.haskell.org/trac/ghc/wiki/Building/GettingTheSources -- since > this is usually what I hit when googling for "ghc git source"... > > Karel > > On 07/13/11 10:37 PM, Jack Henahan wrote: >> I'll see if I can put some work into it tonight. I have a few hours before >> work, so I should be able to put a draft together, unless someone beats me >> to it. >> >> Jack >> >> On Jul 13, 2011, at 9:27 AM, Simon Peyton-Jones wrote: >> >>> Would someone feel able to add instructions on how to use github to build >>> GHC, to the GHC Wiki? It would save folk from re-inventing the wheel. >>> >>> Probably the right place is a fresh page, linked from here: >>> http://hackage.haskell.org/trac/ghc/wiki/Repositories >>> >>> A link to the diagramatic support that github offers (mentioned on this >>> list a couple of weeks back) would be good, as well as a "how to" guide. >>> >>> Simon >>> >>> | -----Original Message----- >>> | From: [email protected] [mailto:[email protected]] On >>> Behalf Of >>> | Johan Tibell >>> | Sent: 12 July 2011 14:48 >>> | To: Karel Gardas >>> | Cc: cvs-ghc >>> | Subject: Re: ghc github.com help... >>> | >>> | On Tue, Jul 12, 2011 at 3:34 PM, Karel Gardas<[email protected]> >>> wrote: >>> |> Hello, >>> |> >>> |> I've forked ghc/ghc repo on github.com to work on ARM port. Now I'd >>> like to >>> |> check it out and compile it, but I'm not able to `sync-all get' since >>> git >>> |> complains with `warning: remote HEAD refers to nonexistent ref, unable >>> to >>> |> checkout.' >>> |> >>> |> I've also tested: >>> |> perl ./sync-all -r http://darcs.haskell.org/git get >>> |> >>> |> in a desperate attempt that git will get all the packages from >>> haskell.org, >>> |> but the result is still the same. >>> |> >>> |> May I ask how the people here are using github.com for their GHC >>> |> development? >>> | >>> | I tested this a moment ago and this works: >>> | >>> | git clone https://github.com/ghc/ghc.git >>> | cd ghc >>> | ./sync-all get >>> | >>> | You'll also want to add your fork as a remote so you can push work to it: >>> | >>> | git remote add tibbe [email protected]:tibbe/ghc.git >>> | >>> | This only adds a remote for the ghc repo, you might also want to add >>> | remotes for other packages you cloned, like testsuite. >>> | >>> | You can now push to your repo: >>> | >>> | git push tibbe master >>> | >>> | Hope this helps. >>> | >>> | Cheers, >>> | Johan >>> | >>> | _______________________________________________ >>> | Cvs-ghc mailing list >>> | [email protected] >>> | http://www.haskell.org/mailman/listinfo/cvs-ghc >>> >>> >>> _______________________________________________ >>> Cvs-ghc mailing list >>> [email protected] >>> http://www.haskell.org/mailman/listinfo/cvs-ghc >> >> >> _______________________________________________ >> Cvs-ghc mailing list >> [email protected] >> http://www.haskell.org/mailman/listinfo/cvs-ghc >> _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
