CLOBBER
author Mozilla Releng Treescript <release+treescript@mozilla.org>
Fri, 12 Apr 2019 15:36:34 +0000
changeset 523153 6b7f2c9b2b4e9d7e78bc02eeb7a0152c96a3a617
parent 521315 a2e7f5c935da4e03d9734b03f43ac62279a1df6b
child 526755 d10b57a89a73db612a1856bee1975e7cdcbe0e7b
permissions -rw-r--r--
No bug - Tagging 03e1b51654e2255fb61a37bb02ed94a7d0637178 with FIREFOX_67_0b10_RELEASE a=release CLOSED TREE DONTBUILD

# 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