Changes between Version 18 and Version 19 of Developer/Contributing


Ignore:
Timestamp:
Mar 4, 2012, 10:46:46 PM (7 years ago)
Author:
Gedare
Comment:

/* Patches */

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Contributing

    v18 v19  
    4040A patch is a text file containing the difference between an old and new version of code. Patches against current development (git head) are preferred to patches against releases unless your patch is intended as a bug fix candidate for a release branch. Send one patch for each logical change made. Each patch you submit should be impossible to subdivide into more patches because of dependencies between the changed parts. Patches that fix code formatting to conform to [wiki:Developer/Coding/Conventions our standards] are best not mixed with substantive changes and vice versa, because the code reformatting hides the functional changes.
    4141
    42 See [wiki:Git_Users#Creating_a_Patch  Creating a Patch] with Git for further details.
     42See [wiki:Git_Users#Creating_a_Patch  Creating a Patch] for details on how to use Git to create patches.
     43
     44If you do not have the Git repository available then you can use the diff program to create a patch by comparing an unmodified RTEMS against the version containing your changes with ''diff -up rtems rtems-new'' and redirect the output to a file.
     45
     46We prefer patches posted as plain text. If the patch is too big posting it gzipped is acceptable but it would be better as a branch that can be pulled/reviewed. Submit your patch to the [wiki:RTEMSMailingLists_  rtems-devel mailing list] and if the patch fixes a bug, file a PR on the [wiki:Bugzilla Bugzilla].
    4347= Submitting =
    4448