commit 882c6a8b6bc8c644c7cc473ea26c9bdd0a5ac30e
parent 5e579f1966d61524ad6c61676f7f1d7e7caafb30
Author: Michael Froman <mfroman@mozilla.com>
Date: Thu, 13 Nov 2025 18:37:45 +0000
Bug 2000025 - commit sha guidance should be in oldest-to-newest order for git like hg. r=dbaker DONTBUILD
It makes it far more tedious if using that last of commit shas as
input to extract-for-git.py if they're in the reverse order. When
running under mercurial, the order is already correct for using with
extract-for-git.py.
Differential Revision: https://phabricator.services.mozilla.com/D272512
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dom/media/webrtc/third_party_build/verify_vendoring.sh b/dom/media/webrtc/third_party_build/verify_vendoring.sh
@@ -47,7 +47,7 @@ echo "LAST_PATCHSTACK_UPDATE_COMMIT_SHA: $LAST_PATCHSTACK_UPDATE_COMMIT_SHA"
# grab the oldest, non "Vendor from libwebrtc" line
if [ "x$MOZ_REPO" == "xgit" ]; then
-CANDIDATE_COMMITS=`git log --format='%h' --invert-grep \
+CANDIDATE_COMMITS=`git log --reverse --format='%h' --invert-grep \
--grep="Vendor libwebrtc" $LAST_PATCHSTACK_UPDATE_COMMIT_SHA..HEAD -- third_party/libwebrtc \
| awk 'BEGIN { ORS=" " }; { print $1; }'`
else
