Changeset 57452 in webkit


Ignore:
Timestamp:
Apr 11, 2010 11:51:59 AM (14 years ago)
Author:
eric@webkit.org
Message:

2010-04-11 Joseph Pecoraro <Joseph Pecoraro>

Reviewed by Eric Seidel.

Minor Updates and Cleanup to the Contributing Page
https://bugs.webkit.org/show_bug.cgi?id=37415

  • coding/contributing.html:
Location:
trunk/WebKitSite
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/WebKitSite/ChangeLog

    r57251 r57452  
     12010-04-11  Joseph Pecoraro  <joepeck@webkit.org>
     2
     3        Reviewed by Eric Seidel.
     4
     5        Minor Updates and Cleanup to the Contributing Page
     6        https://bugs.webkit.org/show_bug.cgi?id=37415
     7
     8        * coding/contributing.html:
     9
    1102010-04-07  Maciej Stachowiak  <mjs@apple.com>
    211
  • trunk/WebKitSite/coding/contributing.html

    r56300 r57452  
    121121<p>There is one ChangeLog per top-level directory, if you changed code and tests you will need to edit at least two ChangeLogs. The <code>prepare-ChangeLog</code> script will create a stub entries for you.  You should edit these stubs to describe your change, including the full url to the bug (<a href="http://trac.webkit.org/changeset/43259">example entry</a>, note that you can use <code>--bug</code> flag).  (You should set EMAIL_ADDRESS and CHANGE_LOG_NAME in your environment if you will be running this script frequently.)</p>
    122122
    123 <p>The line WARNING: NO TEST CASES ADDED OR CHANGED appears if prepare-ChangeLog did not detect the addition of test cases.  If your patch does not require test cases (or test cases are not possible), you should include a line stating such.  Otherwise all changes require test cases which should be mentioned in the ChangeLog.</p>
     123<p>The "No new tests. (OOPS!)" line appears if <code>prepare-ChangeLog</code> did not detect the addition of test cases.  If your patch does not require test cases (or test cases are not possible), you should include a line stating such.  Otherwise all changes require test cases which should be mentioned in the ChangeLog.</p>
    124124
    125125<h3>Create the patch</h3>
     
    132132
    133133<p>The <code>svn-create-patch</code> script does not create a file automatically.
    134 You need to redirect the output yourself using something like--</p>
     134You need to redirect the output yourself using something like:</p>
    135135<p class="code">svn-create-patch > MyExcellentPatch.txt</p>
    136136
Note: See TracChangeset for help on using the changeset viewer.