CLOBBER
author Phil Ringnalda <philringnalda@gmail.com>
Wed, 18 May 2016 00:04:29 -0400
changeset 336858 cbb9d4a22c5c20703b6fedf78c7b27ae7d62d897
parent 334385 146b55a0222202b6eb98f0ead305776d8ae0fc2b
child 337167 efb574fec48e676ee6681c30849af47e3e7e4006
permissions -rw-r--r--
Backed out 3 changesets (bug 1271794, bug 1271829) on suspicion of making Windows builds less likely to... build CLOSED TREE Backed out changeset d0ab0d508a24 (bug 1271829) Backed out changeset 9f4983dfd881 (bug 1271829) Backed out changeset 28b45df659b7 (bug 1271794)

# 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 1265131 - Update Skia to m51 branch