CLOBBER
author Alex Gaynor <agaynor@mozilla.com>
Thu, 30 Mar 2017 09:50:57 -0400
changeset 350487 7bd673cb48e49ba40c28818bec1a3318a2a2a15c
parent 350380 1fbba523a913d69025a63e456b5d422aac1d43a0
child 350816 e87ffc90adf09391144f610ca22cf6fdf3d1d596
permissions -rw-r--r--
Bug 1352055 - Remove reference to a legacy preference name for sandboxing. r=jimm MozReview-Commit-ID: 28UfBrHWfcb

# 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 1337331 - Required because of removed cc files like security/sandbox/chromium/base/threading/platform_thread_linux.cc