diff options
author | Simon Marlow <marlowsd@gmail.com> | 2013-09-23 16:03:44 +0100 |
---|---|---|
committer | Simon Marlow <marlowsd@gmail.com> | 2013-10-01 11:45:46 +0100 |
commit | 2f69aaea7066b8d11034925d9376fadd67361eca (patch) | |
tree | 384711303663047480f88d727a3b5fa3ed90e8d3 /HACKING.md | |
parent | 0b0fec536e35769b64b8bc5397c84138fa512155 (diff) | |
download | haskell-2f69aaea7066b8d11034925d9376fadd67361eca.tar.gz |
Globally replace "hackage.haskell.org" with "ghc.haskell.org"
Diffstat (limited to 'HACKING.md')
-rw-r--r-- | HACKING.md | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/HACKING.md b/HACKING.md index 4fe4d2c921..74a08041d6 100644 --- a/HACKING.md +++ b/HACKING.md @@ -10,14 +10,14 @@ The GHC Developer's Wiki The home for GHC hackers is our Trac instance, located here: -<http://hackage.haskell.org/trac/ghc> +<http://ghc.haskell.org/trac/ghc> From here, you can file bugs (or look them up,) use the wiki, view the `git` history, among other things. Of particular note is the building page, which has the high level overview of the build process and how to get the source: -<http://hackage.haskell.org/trac/ghc/wiki/Building> +<http://ghc.haskell.org/trac/ghc/wiki/Building> Contributing patches to GHC in a hurry ====================================== @@ -25,7 +25,7 @@ Contributing patches to GHC in a hurry Make sure your system has the necessary tools to compile GHC. You can find an overview here: -<http://hackage.haskell.org/trac/ghc/wiki/Building/Preparation> +<http://ghc.haskell.org/trac/ghc/wiki/Building/Preparation> Next, clone the repository and all the associated libraries: @@ -74,7 +74,7 @@ $ Now create a trac ticket: -<http://hackage.haskell.org/trac/ghc/newticket?type=bug> +<http://ghc.haskell.org/trac/ghc/newticket?type=bug> And attach the files in your `patches/` directory. Set the status from *new* to *patch* and we'll review it as soon as we can! @@ -85,22 +85,22 @@ Useful links: An overview of things like using git, the release process, filing bugs and more can be located here: -<http://hackage.haskell.org/trac/ghc/wiki/WorkingConventions> +<http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions> You can find our coding conventions for the compiler and RTS here: -<http://hackage.haskell.org/trac/ghc/wiki/Commentary/CodingStyle> -<http://hackage.haskell.org/trac/ghc/wiki/Commentary/Rts/Conventions> +<http://ghc.haskell.org/trac/ghc/wiki/Commentary/CodingStyle> +<http://ghc.haskell.org/trac/ghc/wiki/Commentary/Rts/Conventions> A high level overview of the bug tracker: -<http://hackage.haskell.org/trac/ghc/wiki/WorkingConventions/BugTracker> +<http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/BugTracker> If you're going to contribute regularly, **learning how to use the build system is important** and will save you lots of time. You should read over this page carefully: -<http://hackage.haskell.org/trac/ghc/wiki/Building/Using> +<http://ghc.haskell.org/trac/ghc/wiki/Building/Using> How to communicate with us ========================== |