CLOBBER
author KuoE0 <kuoe0.tw@gmail.com>
Mon, 09 Jan 2017 17:24:08 +0800
changeset 458402 d41196b0e0d4f448f174f5326138efdb44a37413
parent 454140 126348e718d03dec640b30b5def70fce8aa71527
child 459948 b0853f9cf0b1e7fbd54b5e9a57c20d859e8ccc06
child 460412 ddb6c3191d11308531624d0fd4049792b16d730c
permissions -rw-r--r--
Bug 1329381 - (Part 2) Use the same format like the computed value as the speicified value for background-repeat. r?boris MozReview-Commit-ID: 7vQiivFm1SS

# 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 1250356 Setting CLOBBER out caution landing a huge patchset with gyp changes