Changes between Version 17 and Version 18 of WorkingConventions/FixingBugs

Timestamp:

01/29/13 06:44:06 (4 months ago)

Author:

henrique

Comment:

--

WorkingConventions/FixingBugs

@@ -9 +9 @@
 Some bugs are easy to fix: improvements to documentation, misleading comments, poorly-worded error messages, or egregious little bugs.  In these cases, please just
  * Fix the code
- * Use `git send-email`, or just mail a patch to [mailto:cvs-ghc@haskell.org].  Make sure you include in the patch description a summary of what the problem is, and the nature of your fix.
+ * Use `git send-email`, or just mail a patch to [mailto:ghc-devs@haskell.org].  Make sure you include in the patch description a summary of what the problem is, and the nature of your fix.
 
 This route is easy for you, but more work for us; we have to [wiki:TestingPatches test your fix].  But it's a low-overhead route for easy fixes.
@@ -23 +23 @@
    * Put the name of the test in the "Test Case" field of the Trac report.[[BR]][[BR]]
  0. '''Fix the bug'''!
-   * If your proposed fix has non-local consequences, please consult us (on cvs-ghc@haskell.org) before investing too much of your time.
+   * If your proposed fix has non-local consequences, please consult us (on ghc-devs@haskell.org) before investing too much of your time.
    * Please follow our [wiki:WorkingConventions#Coding coding conventions]
    * Comment your fix in the source code, and include a reference to the bug ticket number, e.g. "`#1466`" (this helps when grepping for the fix later).  It is often helpful to give a small example code fragment that demonstrates the need for your fix.  This isn't always relevant; sometimes you are fixing a plain error, but often it's more subtle than that.[[BR]][[BR]]