CLOBBER
author Kartikaya Gupta <kgupta@mozilla.com>
Tue, 03 Oct 2017 13:15:13 -0400
changeset 384264 01d20d2ebb57d1be52e87e4666e661577335c16e
parent 382192 835a92b19e3d7666890153a84bc635bc43a44cb2
child 387852 17c1e024efc2ac9dd1638c568d70c91548e986dc
permissions -rw-r--r--
Bug 1403971 - Update webrender to commit aa81aebba2c1b8ff8af5d40796154d66349fd131. r=mstange MozReview-Commit-ID: FE8qFq751hv

# 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.

Merge day clobber