# After this point: # * eE: All commands should succeed. # * u: All variables should be defined before use. # * o pipefail: All stages of all pipes should succeed.
set -eEuo pipefail
# grab the oldest, non "Vendor from libwebrtc" line
CANDIDATE_COMMITS=`hg log --template "{node|short} {desc|firstline}\n" \
-r "children($LAST_PATCHSTACK_UPDATE_COMMIT_SHA)::. - desc('re:(Vendor libwebrtc)')" \
--include"third_party/libwebrtc/" | awk 'BEGIN { ORS=" " }; { print $1; }'` echo"CANDIDATE_COMMITS:" echo"$CANDIDATE_COMMITS"
EXTRACT_COMMIT_RANGE="{start-commit-sha}::." if [ "x$CANDIDATE_COMMITS" != "x" ]; then
EXTRACT_COMMIT_RANGE="$CANDIDATE_COMMITS" echo"EXTRACT_COMMIT_RANGE: $EXTRACT_COMMIT_RANGE" fi
ERROR_HELP=$"
***
There are changes detected after vendoring libwebrtc from our local copy
of the git repo containing our patch-stack:
$MOZ_LIBWEBRTC_SRC
Typically this is due to changes made in mercurial to files residing
under third_party/libwebrtc that have not been reflected in
moz-libwebrtc git repo's patch-stack.
The following commands should help remedy the situation:
./mach python $SCRIPT_DIR/extract-for-git.py $EXTRACT_COMMIT_RANGE
mv mailbox.patch $MOZ_LIBWEBRTC_SRC
(cd $MOZ_LIBWEBRTC_SRC && \\
git am mailbox.patch)
After adding the new changes from mercurial to the moz-libwebrtc
patch stack, you should re-run this command to verify vendoring:
bash $0 "
FILE_CHANGE_CNT=`hg status third_party/libwebrtc | wc -l | tr -d " "` if [ "x$FILE_CHANGE_CNT" != "x0" ]; then echo"$ERROR_HELP"
exit 1 fi
echo"Done - vendoring has been verified."
Messung V0.5
¤ Dauer der Verarbeitung: 0.10 Sekunden
(vorverarbeitet)
¤
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.