CLOBBER
author David Anderson <danderson@mozilla.com>
Fri, 25 Mar 2016 01:35:07 -0700
changeset 324104 3c3cb171a6ccc6dbda66bf513b0d33e131d6cfea
parent 323999 51108a6d89630bd07a3251f3bb7c89e25f5d835d
child 324151 dcaf0a6fa115ad73bf7505a8e76464250b971a04
permissions -rw-r--r--
Track whether or not remote layers have acknowledged compositor changes. (bug 1256517 part 1, r=mattwoodrow, a=rkothari)

# 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 1264786 needed a clobber and bug 1254356 hasn't been uplifted to aurora to fix the clobberer