Compare Revisions

Creating a patch

Revision 37809:

Revision 37809 by dlo on

Revision 37810:

Revision 37810 by dlo on

Title:
Creating a patch
Creating a patch
Slug:
Creating_a_patch
Creating_a_patch
Tags:
NeedsTechnicalReview, "Developing Mozilla"
NeedsTechnicalReview, "Developing Mozilla"
Content:

Revision 37809
Revision 37810
t11      After you have <a class="external" href="en/Mercurial" titlt11      After you have <a class="external" href="en/Mozilla_Source_
>e="https://developer.mozilla.org/editor/fckeditor/core/editor/en/>Code_(Mercurial)" title="https://developer.mozilla.org/editor/fck
>Mercurial">obtained the source code</a>, made changes to it, <a h>editor/core/editor/en/Mozilla_Source_Code_(Mercurial)">obtained t
>ref="/en/Build_and_Install" title="en/Build_and_Install">built</a>he source code</a>, made changes to it, <a href="/en/Build_and_In
>> and <a href="/en/Mozilla_automated_testing" title="en/Mozilla_a>stall" title="en/Build_and_Install">built</a> and <a href="/en/Mo
>utomated_testing">tested</a> it (and included your tests in your >zilla_automated_testing" title="en/Mozilla_automated_testing">tes
>patch, if possible), you'll want to get your changes <a href="/en>ted</a> it (and included your tests in your patch, if possible), 
>/Getting_your_patch_in_the_tree" title="en/Getting_your_patch_in_>you'll want to get your changes <a href="/en/Getting_your_patch_i
>the_tree">reviewed and checked in</a>. In order to do that, you n>n_the_tree" title="en/Getting_your_patch_in_the_tree">reviewed an
>eed to create a file listing the changes you made, called a <em>p>d checked in</a>. In order to do that, you need to create a file 
>atch</em> or a <em>diff file</em>. You can generate it using <str>listing the changes you made, called a <em>patch</em> or a <em>di
>ong>cvs diff</strong> or <strong>hg diff</strong> command.>ff file</em>. You can generate it using <strong>cvs diff</strong>
 > or <strong>hg diff</strong> command.

Back to History