CLOBBER
author Iris Hsiao <ihsiao@mozilla.com>
Mon, 14 Nov 2016 11:07:23 +0800
changeset 438353 6adbbb16e04af32c3a358774013638aa8cee2ccd
parent 435852 4d4ee97ad221f9700e228d0f75839a680c0ddba5
child 438410 a516c754042c438a5c1499171ca525a980ecb911
child 491578 8da0a779fdd3a109d235a0cfb6e6810ec4164d76
permissions -rw-r--r--
Backed out changeset e2a5702d96b0 (bug 1306314)

# 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 1277704 - jemalloc may need a clobber