CLOBBER
author Johan Lorenzo <jlorenzo@mozilla.com>
Wed, 12 Apr 2017 14:34:58 +0200
changeset 402417 2d53e3a676bb1617ac701b5470a91ec831bb921b
parent 401831 278c3bf8f7f4a1a8260e1563f18bf93ccb097d24
child 403624 d9618183e8825531cd7b5e4247a57f0d1009f7d0
permissions -rw-r--r--
Bug 1355018 - Make post-release steps use the unified repo r=rail MozReview-Commit-ID: GtfoY8RVE2n

# 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