289
edits
Changes
m
→Creating and submitting a patch: added some DevMo links
Wow! You've fixed the bug you were working on? Fantastic! Time to submit a patch so that everyone can enjoy the fruits of your labor. The first thing to recognize is that the files inside calendar.jar are slightly different from the actual source files. In an ideal world, you'll check out the source code and create your patch based on that. If your changes are small however, your reviewer may be willing to accept a chrome patch for the short term. If you plan on submitting several patches, you really need to work from CVS.
1.) Check out the Mozilla source code. See the [http://developer.mozilla.org/en/docs/Mozilla_Source_Code_Via_CVS DevMo article] for more details on this step.
2.) Open up the relevant files and make the same changes to them that you made to your calendar.jar files.
3.) Use your CVS program's diff utility to create a file that contains information about the files you changed. This is usually done with a command something like
<tt>cvs diff -prU 8 mozilla/calendar/ > myPatch.diff</tt>
See the [http://developer.mozilla.org/en/docs/Creating_a_patch DevMo article] for more details on this step.
4.) Go to the bug you've been working on and choose 'Create an Attachment'. Put the path to the file that CVS diff created in the proper box, and give your patch a short title describing your changes. Describe in detail the changes that you've made in the Description box. Check the 'Patch' checkbox under content type.
