Remove libvpx_new

third_party/libvpx_new/README.chromium

Index: third_party/libvpx_new/README.chromium
diff --git a/third_party/libvpx_new/README.chromium b/third_party/libvpx_new/README.chromium
deleted file mode 100644
index a1d381e4e40ca7e97d747ca9f3e6acc6739b7024..0000000000000000000000000000000000000000
--- a/third_party/libvpx_new/README.chromium
+++ /dev/null
@@ -1,48 +0,0 @@
-Name: libvpx
-URL: http://www.webmproject.org
-Version: v1.4.0
-License: BSD
-License File: LICENSE
-Security Critical: yes
-
-Date: Tuesday February 16 2016
-Branch: master
-Commit: 89cc68252846478fa7f2d570d96ff93776cefac6
-
-Description:
-Contains the sources used to compile libvpx binaries used by Google Chrome and
-Chromium.
-
-The libvpx source is from webmproject.org:
-  http://www.webmproject.org/code/
-  https://chromium.googlesource.com/webm/libvpx
-
-Please follow these steps to update libvpx source code:
-
-1. Update the code:
-     roll_dep.py \
-       -r <libvpx OWNER> \
-       --log-limit 20 \
-       --roll-to <libvpx hash> \
-       src/third_party/libvpx_new/source/libvpx
-
-   Use the generated commit message for the roll.
-
-2. Generate .gypi, .gni and config files.
-
-   cd third_party/libvpx_new
-   ./generate_gypi.sh
-
-3. Update README.chromium with Date, Branch, and Commit.
-
-Tools needed to build libvpx:
-
-- generate_gypi.sh
-
-Generate config and .gypi files that contain the source list for each platform.
-Configuration for the build is taken from vpx_config.h for each platform.
-
-- lint_config.sh
-
-A tool to verify vpx_config.h and vpx_config.asm are matched. This also
-prints the final configuration after checking.