CLOBBER
author Ehsan Akhgari <ehsan@mozilla.com>
Fri, 05 May 2017 22:40:04 -0400
changeset 407409 bcca0465773f8a75863f35f75d6f2594df505c06
parent 405982 d9618183e8825531cd7b5e4247a57f0d1009f7d0
child 407945 0b1371055c7f890ed8cc265726747a35c67ead8f
permissions -rw-r--r--
Back out bug 1357107 since it broke a feature that we have no automated tests for...

# 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 1356927 - Mac builds in automation require a clobber for a change in which ranlib they use