mozilla

Compare Revisions

How to Submit a Patch

Change Revisions

Revision 468795:

Revision 468795 by monad on

Revision 549937:

Revision 549937 by Karlt on

Title:
How to Submit a Patch
How to Submit a Patch
Slug:
Developer_Guide/How_to_Submit_a_Patch
Developer_Guide/How_to_Submit_a_Patch
Tags:
"Developing Mozilla", "Bugzilla"
"Developing Mozilla", "Bugzilla"
Content:

Revision 468795
Revision 549937
t41      If your changes result in a large, complex patch, consider t41      Each patch should represent a single complete change. Separ
>breaking it into several smaller, easy to understand patches, app>ate distinct changes into multiple patches. If your change result
>lied on top of each other (the <a href="/en/Mercurial_Queues" tit>s in a large, complex patch, then see whether it can be broken do
>le="en/Mercurial Queues">mq extension</a> for mercurial can be of>wn into <a href="https://secure.phabricator.com/book/phabflavor/a
> help here). This will make it easier to review your changes, <a >rticle/writing_reviewable_code/#many-small-commits">smaller, easy
>class="external" href="http://groups.google.com/group/mozilla.dev> to understand, patches representing complete steps</a>, applied 
>.planning/msg/2f99460f57f776ef?hl=en" title="http://groups.google>on top of each other (the <a href="/en/Mercurial_Queues" title="e
>.com/group/mozilla.dev.planning/msg/2f99460f57f776ef?hl=en">leadi>n/Mercurial Queues">mq extension</a> for mercurial can be of help
>ng to quicker reviews</a> and better confidence in the review.> here). This will make it easier to review your changes, <a class
 >="external" href="http://groups.google.com/group/mozilla.dev.plan
 >ning/msg/2f99460f57f776ef?hl=en" title="http://groups.google.com/
 >group/mozilla.dev.planning/msg/2f99460f57f776ef?hl=en">leading to
 > quicker reviews</a> and better confidence in the review.

Back to History