3
edits
Media/WebRTC/Legacy Updating Process: Difference between revisions
Jump to navigation
Jump to search
Media/WebRTC/Legacy Updating Process (view source)
Revision as of 17:52, 14 April 2016
, 14 April 2016Added clarification to the extra hg qref step.
(Replaced no longer valid SVN instructions with git instructions.) |
(Added clarification to the extra hg qref step.) |
||
| Line 30: | Line 30: | ||
* hg qnew webrtc_revXXX -m "Bug xxxxxx: Webrtc updated to branch N.MM rev XXXX; pull made <date_from_/tmp/date>" | * hg qnew webrtc_revXXX -m "Bug xxxxxx: Webrtc updated to branch N.MM rev XXXX; pull made <date_from_/tmp/date>" | ||
* hg qref | * hg qref | ||
** | ** If the patch file is very large, which it usually is in this case, hg will not actually create the new patch but show a warning that it is very large. You will need to do the qref in order to finalize that new patch file. If the file has been created, this last step is a no-op. | ||
* hg qpop | * hg qpop | ||
* find the last update changeset - there will be two, one for landing the upstream code, one for the rollup of any changes | * find the last update changeset - there will be two, one for landing the upstream code, one for the rollup of any changes | ||