24
edits
Firefox/Kinto: Difference between revisions
Jump to navigation
Jump to search
Additional instruction to contribute to Gecko
(→Use Cases: Update people names) |
(Additional instruction to contribute to Gecko) |
||
| Line 147: | Line 147: | ||
First, follow [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions the instructions to build Firefox]. | First, follow [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions the instructions to build Firefox]. | ||
In order to speed up the build and being able to run tests properly, create a **mozconfig** file at the root of the repository: | |||
<pre> | |||
ac_add_options --enable-debug | |||
ac_add_options --disable-optimize | |||
ac_add_options --disable-crashreporter | |||
ac_add_options --with-ccache=/usr/bin/ccache | |||
</pre> | |||
For JavaScript updates only, have a look at [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Artifact_builds Artifacts Builds], trading bandwidth for compilation time. | For JavaScript updates only, have a look at [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Artifact_builds Artifacts Builds], trading bandwidth for compilation time. | ||
| Line 228: | Line 237: | ||
See https://wiki.mozilla.org/ReleaseEngineering/TryServer | See https://wiki.mozilla.org/ReleaseEngineering/TryServer | ||
Or use a ''gecko-dev'' fork from Github, and with install [https://github.com/mozilla/moz-git-tools moz git tools] | With Mercurial, push a patch to MozReview (see below) and trigger a Try build from the UI (*Automation > Trigger a Try build*). | ||
Or with git, use a ''gecko-dev'' fork from Github, and with install [https://github.com/mozilla/moz-git-tools moz git tools] | |||
<pre> | <pre> | ||
| Line 239: | Line 250: | ||
<pre> | <pre> | ||
# Keep a bookmark of your branch to address review. | |||
# (equivalent of git branches) | |||
hg bookmark bug/XXXXX | |||
# Commit with link to Bugzilla | # Commit with link to Bugzilla | ||
hg commit -m "Bug XXXXX - Upgrade <lib> to X.Y.Z" | hg commit -m "Bug XXXXX - Upgrade <lib> to X.Y.Z" | ||
| Line 244: | Line 259: | ||
# Submit to MozReview | # Submit to MozReview | ||
hg push review | hg push review | ||
# Go back to «master» | # Go back to «master» | ||
hg update central | hg update -C central | ||
</pre> | </pre> | ||
| Line 255: | Line 267: | ||
* https://reviewboard.mozilla.org/r/45445/ | * https://reviewboard.mozilla.org/r/45445/ | ||
To adjust previously submitted patch: | |||
<pre> | |||
# Go to bookmark | |||
hg update -C bug/XXXXX | |||
# Address comments | |||
... | |||
# Amend commit | |||
hg commit --amend | |||
# Inspect history | |||
hg log -f -G --rev bug/XXXXX | less | |||
# Update review | |||
hg push review | |||
</pre> | |||
When a patch has several commits: | |||
<pre> | |||
# Inspect current branch | |||
hg log -f -G --rev bug/XXXXX | less | |||
# Squash/Reword commits since rev c59308877f9a | |||
hg histedit c59308877f9a | |||
</pre> | |||
To rebase revision c59308877f9a and descendants on last «master»: | |||
<pre> | |||
hg pull | |||
hg rebase -d central -s c59308877f9a | |||
</pre> | |||