Changes between Version 13 and Version 14 of WorkingConventions/FixingBugs


Ignore:
Timestamp:
May 4, 2011 11:23:28 PM (3 years ago)
Author:
dterei
Comment:

darcs -> git

Legend:

Unmodified
Added
Removed
Modified
  • WorkingConventions/FixingBugs

    v13 v14  
    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]] 
    28  0. '''Record a patch''' that embodies your fix.  Please follow our convention for naming patches: [wiki:WorkingConventions/Darcs#PatchNaming].[[BR]][[BR]] 
     28 0. '''Record a patch''' that embodies your fix.  Please follow our convention for naming patches: [wiki:WorkingConventions/Git#PatchNaming].[[BR]][[BR]] 
    2929 0. '''Test your patch''' using the [wiki:TestingPatches validation script], before you submit it.  (If you have write permission to the repository, then you '''must''' validate before pushing the patch.)[[BR]][[BR]] 
    3030 0. '''Submit your patch'''.  If you don't have commit permission for the repository,  
    31    * Use 'darcs format-patch' to create a patch bundle 
     31   * Use 'git format-patch' to create a patch bundle 
    3232   * Attach the patch bundle to the Trac bug report 
    3333   * Add a comment to the Trac bug report to say what you've done