CLOBBER
author Timothy Nikkel <tnikkel@gmail.com>
Wed, 01 Mar 2017 22:45:54 -0600
changeset 345586 7f13c7a84acb0eac18b13cf48cca108b4e26b1d0
parent 345340 af1edb14a70783428bd19329869bd06e6ae74b44
child 345726 08fc65da882241628b387d3d816fcda1d2eed305
permissions -rw-r--r--
Bug 1343341. Create state on the AnimationState object to track whether the image is decoded or not. r=aosmond We end up needing to track a few different things. The large comment in the patch explains.

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

Touching clobber for Bug 1322703 - Use -Fd to specify unique PDB filename per-compile for MSVC