Changes between Version 17 and Version 18 of WorkingConventions/FixingBugs


Ignore:
Timestamp:
Jan 29, 2013 2:44:06 PM (2 years ago)
Author:
henrique
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkingConventions/FixingBugs

    v17 v18  
    99Some bugs are easy to fix: improvements to documentation, misleading comments, poorly-worded error messages, or egregious little bugs.  In these cases, please just 
    1010 * Fix the code 
    11  * 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. 
     11 * 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. 
    1212 
    1313This 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. 
     
    2323   * Put the name of the test in the "Test Case" field of the Trac report.[[BR]][[BR]] 
    2424 0. '''Fix the bug'''! 
    25    * If your proposed fix has non-local consequences, please consult us (on cvs-ghc@haskell.org) before investing too much of your time. 
     25   * If your proposed fix has non-local consequences, please consult us (on ghc-devs@haskell.org) before investing too much of your time. 
    2626   * Please follow our [wiki:WorkingConventions#Coding coding conventions] 
    2727   * 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]]