CLOBBER
author Mozilla Releng Treescript <release+treescript@mozilla.org>
Mon, 01 Jun 2020 10:15:55 +0000
changeset 2929014 0524e3719d9d5d43ed9fa02d08576778aca8071f
parent 2907280 9c6d6a6348256a1e350b08751bcbad7c75440ce2
child 2977915 032ea3d97509794563b3b75d49e2054846a56997
child 3010816 7be1c02ed21af0f5868296525ab7c64daf14c28b
child 3016663 8c37d998848127df6d38df46cc220ee3e809e7be
child 3041361 972da45e496bbd4bead1dedad08631b337cb9217
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