CLOBBER
author Emilio Cobos Álvarez <emilio@crisal.io>
Wed, 23 May 2018 20:11:22 +0200
changeset 423087 ee6d7b68769f8a889b9217c82f932683aa707f1e
parent 421491 01997380f76db787f84b14bc34031b8fef3c6c4b
child 423555 b2919970d120b33932ab3a28eb63bac865c3956e
permissions -rw-r--r--
No bug - Remove some cfgs. r=me DONTBUILD, since this is not part of the build. MozReview-Commit-ID: 90UkG6QJWq

# 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 1459785 - ANGLE update; moved files require clobber due to bug 1421146.