CLOBBER
author Matt Howell <mhowell@mozilla.com>
Wed, 24 Aug 2016 10:01:10 -0700
changeset 315853 0bf376ad9b85c1eb5ec3707428151390788976a1
parent 315826 98eb5919336965816379b64f68c732e4d19b66fe
child 316035 cc4bdd6afea0ccacdd2ffec3a294ff97e47474c6
child 316043 9cba6697ae68563dfc87b4131dcf83683d9de8e7
permissions -rw-r--r--
Bug 1292360 - Add attribution data to the telemetry environment block; r=gfritzsche, data-review=bsmedberg MozReview-Commit-ID: 4sltJYJrrFS

# 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