CLOBBER
author Carsten "Tomcat" Book <cbook@mozilla.com>
Thu, 23 Mar 2017 08:41:38 +0100
changeset 349014 f7b3ed3f4674d2b37fc143730c1a06049b7c9820
parent 348984 21f183c27eba2f0f853a877df2866f8825b2bae1
child 350287 4e53b8baa32e585d11c4f591eba3df63ec4d7736
permissions -rw-r--r--
Backed out changeset b6422d885f48 (bug 1342863)

# 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 1343682 - backing out a previous version didn't stop the failures from it, so it appears to need a clobber both out and in