24
edits
Media/WebRTC/libwebrtc Update Process: Difference between revisions
Media/WebRTC/libwebrtc Update Process (view source)
Revision as of 19:03, 30 June 2023
, 30 June 2023Moved comment relevant to prep-repo up to the Update Steps section
(Clarify extract-for-git.py some more) |
(Moved comment relevant to prep-repo up to the Update Steps section) |
||
| Line 41: | Line 41: | ||
# Run loop-ff.sh | # Run loop-ff.sh | ||
bash dom/media/webrtc/third_party_build/loop-ff.sh | bash dom/media/webrtc/third_party_build/loop-ff.sh | ||
Running <code>prep-repo.sh</code> with a fresh github clone of moz-libwebrtc will likely display instructions on how to add recent moz-central changes made in <code>third_party/libwebrtc</code> to the top of the patch stack in github. This is expected and necessary for successfully vendoring changes into <code>third_party/libwebrtc</code>. | |||
=== Push to elm === | === Push to elm === | ||
| Line 83: | Line 85: | ||
=== Operational notes === | === Operational notes === | ||
* 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: | ||