X-Git-Url: http://git.megacz.com/?p=ghc-hetmet.git;a=blobdiff_plain;f=HACKING;h=8ceff18881a9e246c0435535a99cdbb72dd92a60;hp=74aa74288df8b0545c84222a2f0eb7b238166ea2;hb=3391a03562d4056de7b16cd0f632e6c43ae44cca;hpb=b4d59b7caa9dd5816dcdd07a1be94ebd3e6b06d5

diff --git a/HACKING b/HACKING
index 74aa742..8ceff18 100644
--- a/HACKING
+++ b/HACKING
@@ -20,19 +20,32 @@ The GHC Developer's Wiki
   
   Quick Start for developers
 
-     http://hackage.haskell.org/trac/ghc/wiki/Building/Hacking 
-   
-     This section on the wiki will get you up & running with a 
-     serviceable build tree in no time:
-  
+     http://hackage.haskell.org/trac/ghc/wiki/Building/Hacking
+
+     This section on the wiki will get you up and running with a
+     serviceable build tree in no time.
+
+     Don't skip this!  By default, GHC builds with all optimizations
+     and profiling; most hackers will want a quicker build, so creating
+     a mk/build.mk file and knowing how to rebuild only parts of GHC is
+     very important.
+
      This is part of the "Building GHC" section of the wiki, which
      has more detailed information on GHC's build system should you
      need it.
+
+
+  Coding conventions
+
+     http://hackage.haskell.org/trac/ghc/wiki/WorkingConventions
+
+     This wiki page explains the ground rules for code that is intended
+     to go into the mainline compiler source.
   
   
   The GHC Commentary
   
-     http://hackage.haskell.org/trac/wiki/Commentary
+     http://hackage.haskell.org/trac/ghc/wiki/Commentary
 
      Notes on the internals and architecture of GHC.
      
@@ -41,7 +54,7 @@ Mailing lists
 -------------
 
    Ask on glasgow-haskell-users@haskell.org if you have difficulties.
-   If you're working with the current CVS sources of GHC, then
+   If you're working with the current darcs sources of GHC, then
    cvs-ghc@haskell.org might be a more appropriate (developers hang
    out here).  See http://www.haskell.org/mailman/listinfo for
    subscription.