Meta-bug for tracking any issues related to updating libyuv.

MozReview-Commit-ID: 3MK84gHSrLg

MozReview-Commit-ID: CDMDXqpGueS

Comment on attachment 8839979 [details] [diff] [review] Create new update script for libyuv Review of attachment 8839979 [details] [diff] [review]: ----------------------------------------------------------------- Update script looks good. r=me with the README_MOZILLA issue fixed. The patches look plausible, but I think sotaro should review them for correctness and sufficiency. ::: media/libyuv/README_MOZILLA @@ +1,1 @@ > + It's nice to have a file like this with the imported version and upstream url, but this copy seems to be empty? I think you need to seed the file with the expected text for the substitution function in update.py to work. Something like: YUV-format image scaling and conversion library The source in this directory was copied from upstream by running the update.py script. Any changes made relative to upstream should be reflected in that script, e.g. by applying patch files after the copy step. The upstream repository is https://chromium.googlesource.com/libyuv/libyuv The git commit ID used was r6102.

Pushed by rjesup@wgate.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/946da1e13208 Create new update script for libyuv r=sotaro,rillian https://hg.mozilla.org/integration/mozilla-inbound/rev/c560b9eed8b1 Fix build fallout from moving libyuv into a subdirectory r=ted

https://hg.mozilla.org/mozilla-central/rev/946da1e13208 https://hg.mozilla.org/mozilla-central/rev/c560b9eed8b1

For the future libyuv upstream updates, let's aim to land the changes during the first half of the nightly cycle, unless we have a really good reason to do it closer to the train change.

The leave-open keyword is there and there is no activity for 6 months. :jesup, maybe it's time to close this bug?