Confirmed users
400
edits
(→Building Fennec: Add some links for mercurial bookmark usage.) |
|||
Line 262: | Line 262: | ||
To speed up subsequent builds you should specify the android directory using "./mach build mobile/android" or "./mach build mobile/android/base" depending on where your changes are. | To speed up subsequent builds you should specify the android directory using "./mach build mobile/android" or "./mach build mobile/android/base" depending on where your changes are. | ||
=== Mercurial tips === | |||
Mercurial (hg) is the the main version control system that Mozilla uses, and to submit code for review, you should be able to generate patches or commits. Be sure to run "mach mercurial-setup" when cloning the repo - this should get you set up with some good default settings and extensions. | |||
The most conceptually simple way to submit changes is using [https://developer.mozilla.org/en-US/docs/Mercurial_Queues patch queues] to generate patches to upload to bugzilla, where they can be reviewed. | |||
However, Mozilla developers are moving away from patch-based workflow to hg-bookmark-based development. As of yet, this isn't fully codified, but the following are a few good resources for a bookmark-based workflow: | |||
* [http://mercurial.selenic.com/wiki/Bookmarks Using bookmarks] | |||
* [http://jordi.inversethought.com/blog/customising-mercurial-like-a-pro/ Repo state visualizations] | |||
Greg Szorc (:gps) has also put together a [https://people.mozilla.org/~gszorc/mastering-vcs/#9 set of slides] that are good supplemental material for understanding hg workflow. His [http://gregoryszorc.com/blog/category/mercurial/3/ blog] is another good place to follow version control changes at Mozilla. | |||
== Hacking == | == Hacking == |