CLOBBER
author Margaret Leibovic <margaret.leibovic@gmail.com>
Wed, 11 Jun 2014 12:08:35 -0700
changeset 208988 5d3393c154010b7a95e3e2b30ac0a5c10c86e7f3
parent 208811 18c21532848a1673c6c3fe57e710fbf6e9cb35e1
child 209520 957b31f09f9e18658eeaee1cfb740bdf084d8231
permissions -rw-r--r--
backout 25fb66c1006f for test failure on a CLOSED TREE

# 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 984528 - Rename manifestdestiny -> manifestparser needs a clobber