CLOBBER
author Jonathan Watt <jwatt@jwatt.org>
Tue, 14 Jan 2014 12:40:01 +0000
changeset 164565 192c2dddd68f8c1605415dda377d68575999851f
parent 164511 00585fe8196f651297a493b542ac34421ff7a3d2
child 164668 840b3469bd0140b03ba24ae37f2674e89650b601
permissions -rw-r--r--
Bug 949891 - Make nsNumberControlFrame a leaf frame so that only its CreateAnonymousContent method can create child frames. r=dholbert

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

CLOBBER due to recent changes to JS build files that were causing
"STOP! configure has changed and needs to be run in this build directory." bustage