CLOBBER
author Sylvestre Ledru <sledru@mozilla.com>
Thu, 10 May 2018 19:05:30 +0200
changeset 417814 06ceda084d694d1687a669995d457ebd6fd0b08e
parent 417247 2d95d70298e248161b629ef1d0d57049c0b62d71
child 418406 1eb04a9bfb7a82eb6fac5e29be7c6b03999d9361
permissions -rw-r--r--
Bug 1460402 - Create a new class to manage pip install r=ahal MozReview-Commit-ID: JnscCmC4gBt

# 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.

Merge day clobber