Fix the SPECIALISE error in the haddock invocation of validate

[ghc-hetmet.git] / HACKING

diff --git a/HACKING b/HACKING
index 9e574cf..8ceff18 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -20,19 +20,32 @@ The GHC Developer's Wiki
   
   Quick Start for developers
 
   
   Quick Start for developers
 

-     http://hackage.haskell.org/trac/ghc/wiki/Building/Hacking 
-   
+     http://hackage.haskell.org/trac/ghc/wiki/Building/Hacking
+

      This section on the wiki will get you up and running with a
      This section on the wiki will get you up and running with a

-     serviceable build tree in no time:
-  
+     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.
      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
   
   
   
   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.
      
 
      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.
 -------------
 
    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.
    cvs-ghc@haskell.org might be a more appropriate (developers hang
    out here).  See http://www.haskell.org/mailman/listinfo for
    subscription.