CLOBBER
author Simon Fraser <sfraser@mozilla.com>
Mon, 22 Jan 2018 11:19:18 +0000
changeset 455160 3d23e6d98a09a3395bf2b0d9cb03dd4be358c715
parent 449644 f6b4d071186895efd54fec3c529c86ab4d451395
child 460790 15334014dc6752581cab545eb7c9f94d725a8bc5
child 462287 a45d6d58a07d2f999b285e9a821822a21bd69ac4
permissions -rw-r--r--
Update configs. IGNORE BROKEN CHANGESETS CLOSED TREE NO BUG a=release ba=release

# 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