CLOBBER
author Maja Frydrychowicz <mjzffr@gmail.com>
Thu, 10 Mar 2016 15:44:59 -0500
changeset 288100 37009016af6a8e13c594fa69c8e5ab74077b374d
parent 287509 ac43f8ec3958d0ba23310aee47d905dd40c1bf6a
child 288739 e2974ac0c94f60d020a7679c18f17a9b918b4ce1
permissions -rw-r--r--
Bug 1255196 - Include mozinfo.json in common.tests.zip; r=gps MozReview-Commit-ID: BJnXphkKJFy

# 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 1253431 - Testing to see if a clobber fixes OSX debug build issues