CLOBBER
author Jeff Gilbert <jgilbert@mozilla.com>
Thu, 09 Feb 2017 20:31:36 -0800
changeset 397399 09487aeae4a72c541fe24e9eeae640cbc9340d7d
parent 396530 b7e42143bbbc9dc3e5c05bd1e93b6485ce1d0ad4
child 395194 5a61fb051d94fe154fa37a00a01d5061ddd0a23b
permissions -rw-r--r--
Bug 1339256 - Detect robust_buffer_access_behavior. - r=daoshengmu MozReview-Commit-ID: 4w5D9bOQbY8

# 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