122
edits
Media/WebRTC/libwebrtc Update Process: Difference between revisions
Media/WebRTC/libwebrtc Update Process (view source)
Revision as of 20:36, 15 June 2023
, 15 June 2023updated path to log file for loop-ff
(Now that some steps have been move, we can simplify some of the prereqs.) |
(updated path to log file for loop-ff) |
||
| Line 72: | Line 72: | ||
* If loop-ff.sh reveals an issue that is best dealt with in a followup, one can commit a temporary patch marked with <code>REPO-elm</code> in the first line of its description, i.e. the "title". The temporary commit allows loop-ff.sh to continue, whereas <code>REPO-elm</code> makes sure the commit cannot be pushed to any other mozilla repo than elm (and try). | * If loop-ff.sh reveals an issue that is best dealt with in a followup, one can commit a temporary patch marked with <code>REPO-elm</code> in the first line of its description, i.e. the "title". The temporary commit allows loop-ff.sh to continue, whereas <code>REPO-elm</code> 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: | ||
tail -f | tail -f .moz-fast-forward/logs/log-loop-ff.txt | grep loop-ff | ||
* If a particularly complicated rebase conflict is encountered, it is helpful to tar up the moz-libwebrtc directory to allow a complete reset without losing current progress. | * If a particularly complicated rebase conflict is encountered, it is helpful to tar up the moz-libwebrtc directory to allow a complete reset without losing current progress. | ||
(cd {path-to}/moz-central && rm log_resume.txt) # resets the resume logic in loop-ff.sh | (cd {path-to}/moz-central && rm log_resume.txt) # resets the resume logic in loop-ff.sh | ||