CLOBBER
author Phil Ringnalda <philringnalda@gmail.com>
Thu, 22 Sep 2016 19:57:04 -0700
changeset 357784 c2d98ee4132a82ee88ad82cc2462d127d342f5dd
parent 357774 11e6496ab698a88c0e08b8141485380e0eeef364
child 358663 826cc48624a31a2755c23bfe83535311df1567bc
permissions -rw-r--r--
Backed out 2 changesets (bug 1304815) for continuing to fail to build on OS X despite being clobbered twice CLOSED TREE Backed out changeset 11e6496ab698 (bug 1304815) Backed out changeset a2cbbd85a818 (bug 1304815)

# 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