CLOBBER
author Jonathan Watt <jwatt@jwatt.org>
Fri, 24 May 2013 18:32:33 +0100
changeset 144426 e3e70237a47af84f9a496b5c9a8094e3a752bd01
parent 144359 4de82dd4b7b6c972e2e1b917e0e39b239b872bb8
child 144515 92393d40a42a47bc6050c88a2674fbb4f52a0eee
permissions -rw-r--r--
Bug 854765 - Get rid of the DidSetStyleContext overrides in SVG frame code to avoid some major perf hits. r=roc

# 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/
#
Bug 874640 touched webidl, so Windows needs to clobber + Bug 854517: Integrate valgrind into B2G builds

Alternative to clobber is to run ./config.status from the objdir and to
touch the CLOBBER file in the objdir.