CLOBBER
author ffxbld <release@mozilla.com>
Mon, 29 Jun 2015 13:34:02 -0700
changeset 281351 d480e05bd2764e680a6982c650092a6fdc13fcfd
parent 280440 de1ddaec57b7434b11528068e9a59c8c5716dd0f
child 281416 f49571596d6f0c25c20e848c47f1d267ec503227
child 282391 f30e1413ebd1d845d7461dfc63bc35c7b627e359
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