CLOBBER
author Aki Sasaki <asasaki@mozilla.com>
Tue, 27 Sep 2016 12:45:22 -0700
changeset 360648 e809e1f8304bc3e76ee5f9cdf4691a0d24b35e29
parent 360035 c2d98ee4132a82ee88ad82cc2462d127d342f5dd
child 360914 826cc48624a31a2755c23bfe83535311df1567bc
permissions -rw-r--r--
bug 1298553 - enable chain of trust generation in the decision task. r=dustin MozReview-Commit-ID: 7lmGt8weVgd

# 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