CLOBBER
author Ryan VanderMeulen <ryanvm@gmail.com>
Wed, 17 Sep 2014 14:39:17 -0400
changeset 205836 d2c01d77b9d0bf344d3a570dd224c4c543f47bba
parent 205547 b771f9a5d4914b1286eabc7857733d088b82e657
child 205925 d4c43e87d458bf86a7c05fc5c784a26b130e2c54
permissions -rw-r--r--
Backed out changesets a68c9d18ffa5 and 750e7aaf09cb (bug 1067414) for causing bug 1068658. a=me

# 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 1063304 needed a clobber.