CLOBBER
author Jonathan Kew <jkew@mozilla.com>
Fri, 01 Jul 2016 23:58:31 +0100
changeset 342050 70ca7c42db312a2a07aad0560aff0bd1fc48de02
parent 341602 cea65ca3d0bdd8325dc556f6bfde6277fc83fe6e
child 342177 77ab901796819a9ab2e820d6bb9350e610786f07
child 343891 a08f7952eebaa20f82c83644ae228e4cc3e46d25
permissions -rw-r--r--
Bug 1254026 - followup - Apply the same fix to the Print dialog. r=emk a=gchang

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

Merge day clobber