CLOBBER
author Mark Hammond <mhammond@skippinet.com.au>
Thu, 15 May 2014 12:00:59 +1000
changeset 192307 107fdcd0b14623e078f1fc9e9217a6fe8f7ea8c1
parent 190773 b56dd8bf8150c946aa9e0538cabfe8a6bd0bcd96
child 192421 4fd82c282519f5185a9e4282ad1f6eb47434d334
child 192456 ff97f449b232818fdd439c34f0d121f88d7d33a8
permissions -rw-r--r--
Bug 1006943 - Non-sensitive FxA log info is included with sync logs. r=rnewman, a=lsblakk

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

Bug 983185 requires a clobber. This may not affect all platforms.