119
edits
Media/WebRTC/libwebrtc Update Process: Difference between revisions
add note to save the patch stack after writing a fix-commit
(Clarify bug number when fixing build failures) |
(add note to save the patch stack after writing a fix-commit) |
||
| Line 58: | Line 58: | ||
* When making changes to fix build issues in moz-libwebrtc (any changes under third_party/libwebrtc), mercurial commit messages follow the pattern: | * When making changes to fix build issues in moz-libwebrtc (any changes under third_party/libwebrtc), mercurial commit messages follow the pattern: | ||
Bug {current-fast-forward-bug-number} - (fix-{upstream-sha}) {description} | Bug {current-fast-forward-bug-number} - (fix-{upstream-sha}) {description} | ||
# then run | |||
(source dom/media/webrtc/third_party_build/use_config_env.sh ; | |||
./mach python dom/media/webrtc/third_party_build/save_patch_stack.py \ | |||
--repo-path $MOZ_LIBWEBRTC_SRC \ | |||
--target-branch-head $MOZ_TARGET_UPSTREAM_BRANCH_HEAD ) | |||
* When making changes to fix Mozilla code (code outside of third_party/libwebrtc) in response to changes upstream, mercurial commit messages follow the pattern: | * When making changes to fix Mozilla code (code outside of third_party/libwebrtc) in response to changes upstream, mercurial commit messages follow the pattern: | ||
Bug {current-fast-forward-bug-number} (MOZ) - {description} | Bug {current-fast-forward-bug-number} (MOZ) - {description} | ||