canmove, Confirmed users
2,850
edits
Partnering/Repacks/Policy and Process: Difference between revisions
Partnering/Repacks/Policy and Process (view source)
Revision as of 16:31, 25 June 2013
, 25 June 2013→Creating a patch
ChrisCooper (talk | contribs) (Created page with "= Version Control = Mozilla keeps all of our partner repack configuration files under version control in [http://mercurial.selenic.com/ Mercurial (hg)]. If you are unfamiliar...") |
ChrisCooper (talk | contribs) |
||
| Line 11: | Line 11: | ||
= Creating a patch = | = Creating a patch = | ||
hg | This section assumes that you are already familiar with the basics of hg. | ||
Here is a generalized workflow: | |||
* clone the partner-repacks repo | |||
** if you already have the repo, run <code>hg pull</code> instead | |||
* make sure you don't have any existing changes in source clone by running <code>hg status</code> | |||
* make any necessary changes to your partner repack files | |||
** make sure you run <code>hg add</code> to add new files, or <code>hg remove</code> if you are removing files | |||
* commit changes to your local repository, <code>hg commit ...</code> | |||
* export the changeset using <code>hg export REV</code>, where REV is the revision number of the changeset, e.g.: | |||
$ PARTNERNAME=aol | |||
$ hg export tip > repack_config_changes_for_$PARTNERNAME.diff | |||
= Submitting a patch = | = Submitting a patch = | ||
TODO: bug filing template | TODO: bug filing template | ||