CLOBBER
author shindli <shindli@mozilla.com>
Fri, 14 Sep 2018 16:35:23 +0300
changeset 494772 c5fbbf959e23a4f33d450cb6c64ef739e09fbe13
parent 493008 bade35bc346f3bc1f5e8b59d3d49c7a1ba28166c
child 498071 be74e0c5c16433b1d7d2cba53565f8b7f6681700
permissions -rw-r--r--
Backed out changeset aae4f349fa58 (bug 1479503) per developer's request on IRC a=backout

# 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