CLOBBER
author Andrea Marchesini <amarchesini@mozilla.com>
Tue, 10 Jan 2017 21:30:28 +0000
changeset 356881 44518b9776d40c85da56f486f16a3a6d26337c3f
parent 355430 126348e718d03dec640b30b5def70fce8aa71527
child 357147 ddb6c3191d11308531624d0fd4049792b16d730c
child 371039 b0853f9cf0b1e7fbd54b5e9a57c20d859e8ccc06
permissions -rw-r--r--
Bug 1329744 - AudioBuffer ctor updated, r=padenot

# 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 1250356 Setting CLOBBER out caution landing a huge patchset with gyp changes