CLOBBER
author Brian Hackett <bhackett1024@gmail.com>
Fri, 16 Aug 2019 20:51:12 +0000
changeset 488604 de8dd803924f6502ea2bcb021b4c9395291dd54d
parent 481751 b1fb07b422487a421a3c4f4423e054e60081f885
child 489391 620c55d58580bf3af2470c303be3ce6cde0b2f86
permissions -rw-r--r--
Bug 1573938 - Never collect wrapper JSObjects when recording/replaying, r=mccr8. Differential Revision: https://phabricator.services.mozilla.com/D42011

# 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.

Merge day clobber