CLOBBER
author Jeff Muizelaar <jmuizelaar@mozilla.com>
Thu, 17 Sep 2015 11:21:10 -0400
changeset 587446 28c92e70bce970c66c6ee70a04789b2c8118944f
parent 579569 7364ae67d69e4b0579de19296f354f0fef26335f
child 582812 0bea3267f101dd2e0f9700c92ebdc74f520df22b
child 589803 039a8490891595736b16a3ccb17f025f4dcf13eb
child 652487 6229055e03575dba741ed5123d63349b8351d83b
permissions -rw-r--r--
try: -b do -p all -u all -t none

# 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 1201224 - stop unifying test package during mac universal builds needed a CLOBBER