CLOBBER
author Phil Ringnalda <philringnalda@gmail.com>
Wed, 22 Mar 2017 19:59:41 -0700
changeset 348984 21f183c27eba2f0f853a877df2866f8825b2bae1
parent 347716 8087b31816d4d795a49d8d2d1b5be16161766f86
child 350287 4e53b8baa32e585d11c4f591eba3df63ec4d7736
permissions -rw-r--r--
Bug 1343682 followup, touch CLOBBER since the previous backout didn't actually stop the failures

# 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