CLOBBER
author ffxbld
Fri, 26 May 2017 08:16:53 -0700
changeset 360774 43b0fdd5b94a28a6b8f4da567b9e6af46a6b5d8e
parent 360079 589fca202ae60ae457d3622b0ab006ae41eb9f85
child 362829 ff64a7889c1fac56d48205fc2fad4eb5aa481a73
permissions -rw-r--r--
No bug, Automated blocklist update from host bld-linux64-spot-301 - a=blocklist-update

# 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.

Bug 1361661 - Update Telemetry build and headers.