CLOBBER
author ffxbld <release@mozilla.com>
Tue, 10 Jan 2017 07:51:35 -0800
changeset 357141 c0657ef3e5a630e6eabf4cb54a5a6cd188bf99fe
parent 355659 5dddbefdf759f09b1411f33fa0920835b919fc81
child 357774 11e6496ab698a88c0e08b8141485380e0eeef364
permissions -rw-r--r--
No bug - Tagging ce55e4d276031458f0730d481acff05d7c797038 with FIREFOX_51_0b13_BUILD1, FIREFOX_51_0b13_RELEASE a=release CLOSED TREE

# 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