CLOBBER
author Jeff Walden <jwalden@mit.edu>
Tue, 27 Mar 2018 12:26:10 -0700
changeset 463900 64eaee27492a1a37905780f7cac1bbe83a305021
parent 463899 10e682fef4a64676dad1dc922e8e6b22ccb9171e
child 464227 122d31260faaad8981c779d3f90fe56bdcdcfa8a
permissions -rw-r--r--
Bug 1449051 - Consolidate the definition of JS::Value::layout to be more readable/understandable and to common up the parts that are common across endianness/word size. r=jandem

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

More ICU-build-related touching for bug 1447475, trying a CLOBBER after a previous build failure just in case.