CLOBBER
author Jonas Finnemann Jensen <jopsen@gmail.com>
Tue, 24 Jan 2017 18:44:37 -0800
changeset 944318 7b675ba466cb9da9cf770bb2fa55dc15c46e1bd2
parent 936425 70a5310085fa0c77bfcf88c4180c3e3af438a44d
child 936806 c52fa5ad5b28d10afb19beb3d2d9e7769d3b74d6
child 938665 2e84d5fecdcdbf8089abf3be3a10f18bd9b12ff5
child 941535 5a4412474c63e1d9e66036d603ac42e9cb2b9150
permissions -rw-r--r--
Bug 1332506 - Treeherder actions defined in-tree. r?dustin MozReview-Commit-ID: BBmrQNXE6Jh

# To trigger a clobber replace ALL of the textual description below,
# giving a bug number and a one line description of why a clobber is
# required. Modifying this file will make configure check that a
# clobber has been performed before the build can continue.
#
# MERGE NOTE: When merging two branches that require a CLOBBER, you should
#             merge both CLOBBER descriptions, to ensure that users on
#             both branches correctly see the clobber warning.
#
#                  O   <-- Users coming from both parents need to Clobber
#               /     \
#          O               O
#          |               |
#          O <-- Clobber   O  <-- Clobber
#
# Note: The description below will be part of the error message shown to users.
#
# Modifying this file will now automatically clobber the buildbot machines \o/
#

# Are you updating CLOBBER because you think it's needed for your WebIDL
# changes to stick? As of bug 928195, this shouldn't be necessary! Please
# don't change CLOBBER for WebIDL changes any more.

Bug 1223692 vp8/common/loopfilter.c removed.