CLOBBER
author Liang-Heng Chen <xeonchen@gmail.com>
Fri, 09 Jun 2017 15:11:24 +0800
changeset 363312 e5fe50da0571a67e4ad62aeb9e13013eba5369c8
parent 362829 ff64a7889c1fac56d48205fc2fad4eb5aa481a73
child 363446 b99b018d5f005aca15fe4a57418b96b6826fdcd7
permissions -rw-r--r--
Bug 1371550 - create worker thread before it is required; r=bagder MozReview-Commit-ID: 9DydRQwOHyT

# 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 1346025 - Move vendored python modules to /third_party/python (need to clobber virtualenv)