CLOBBER
author Wes Kocher <wkocher@mozilla.com>
Wed, 07 Sep 2016 14:22:21 -0700
changeset 312974 ab70808cd4b6c6ad9a57a9f71cfa495fcea0aecd
parent 312802 a46f0e32289bb8975eef7f87d14cbd71c9c10582
child 313598 869a5b6dae7834e2d33e92486b5fd9629f6c3000
permissions -rw-r--r--
Backed out 2 changesets (bug 1283919) for being the wrong way to fix this a=backout Backed out changeset a328778db08d (bug 1283919) Backed out changeset 7e1f25f59298 (bug 1283919)

# 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 1287426 - Clobber required because of Linux Chromium sandbox file moves.