CLOBBER
author Nathan Froyd <froydnj@mozilla.com>
Thu, 10 Jan 2019 10:52:51 -0500
changeset 453267 6d7562d605900b71a5553e368ababe8abb0b7d43
parent 449684 68151063d1c63ce445d67aa743a018d7f66fbb4d
child 459531 149562860c062593ef71b37703d9e20e03cf7b43
permissions -rw-r--r--
Bug 1514043 - change gecko media plugin process name; r=mccr8,bobowen,haik,chutten The only visible change from this change is that telemetry will be discontinuous. The owners for the relevant telemetry probes have reviewed this and indicated that this discontinuity is OK.

# 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