7
edits
Media/WebRTC/libwebrtc Update Process: Difference between revisions
Jump to navigation
Jump to search
Media/WebRTC/libwebrtc Update Process (view source)
Revision as of 22:38, 13 March 2023
, 13 March 2023Add an operational note on repo locking (REPO-elm)
(Remove manual instructions to rebase floating patches (the arcconfig patch really)) |
(Add an operational note on repo locking (REPO-elm)) |
||
| Line 56: | Line 56: | ||
- When making changes to fix Mozilla code in response to changes upstream, mercurial commit messages follow the pattern: | - When making changes to fix Mozilla code in response to changes upstream, mercurial commit messages follow the pattern: | ||
Bug xxx (MOZ) - {description} | Bug xxx (MOZ) - {description} | ||
- If loop-ff.sh reveals an issue that is best dealt with in a followup, one can commit a temporary patch marked with REPO-elm in the first line of its description, i.e. the "title". The temporary commit allows loop-ff.sh to continue, whereas REPO-elm makes sure the commit cannot be pushed to any other mozilla repo than elm (and try). | |||
- While loop-ff.sh is running, in a separate terminal window it may be helpful to see the overall progress by running: | - While loop-ff.sh is running, in a separate terminal window it may be helpful to see the overall progress by running: | ||