Changes between Version 5 and Version 6 of TestingPatches

Timestamp:

08/01/08 01:45:52 (5 years ago)

Author:

simonpj

Comment:

--

TestingPatches

@@ -1 @@
-= Testing Patches =
+= Validating Patches =
 
 Nowadays there are many people working on GHC, which is a Good Thing, but it does mean that many people are inconvenienced if a patch is pushed which makes the HEAD unbuildable. To try to reduce the number of times this happens, we now have a stricter policy for testing patches before committing them.
@@ -5 +5 @@
 In order to test your patches:
  * Get a repository containing the latest HEAD, the patches you want to push, and no other patches or unrecorded changes. Depending on what you are doing, your working repository might be appropriate; otherwise you might prefer to keep a separate repository just for patch testing.
- * In the root directory of the tree, run `sh validate`. This will do a "quick" build and then run the testsuite in "fast" mode. Do not push if any of the tests give unexpected results!
+
+ * In the root directory of the tree, run
+{{{
+sh validate
+}}}
+ This will do a "quick" build and then run the testsuite in "fast" mode. Do not push if any of the tests give unexpected results!
+
  * Depending on the nature of the changes, more testing might be sensible. e.g. if possible, build system changes should be tested on Linux, Mac OS X and Windows machines.  Look at the full documentation for the [wiki:Building/RunningTests test suite].