CLOBBER
author ffxbld <release@mozilla.com>
Mon, 13 May 2019 10:35:27 +0000
changeset 535461 77e0fe8dbdd3384fb8407cdad5be64a18ca6182e
parent 529822 d10b57a89a73db612a1856bee1975e7cdcbe0e7b
child 536638 3d9d20f173e3c76e1f4adfa703d2c3b09ddff7d8
child 538503 d73949bd98e99a892a282a85b68aeb44cd972ffc
permissions -rw-r--r--
Update configs. IGNORE BROKEN CHANGESETS CLOSED TREE NO BUG a=release ba=release

# 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