CLOBBER
author Chris Peterson <cpeterson@mozilla.com>
Tue, 20 Feb 2018 01:47:57 -0800
changeset 472683 f5f49315fec2505facfb775a417bdcf35504b5ef
parent 472569 1eb04a9bfb7a82eb6fac5e29be7c6b03999d9361
child 474795 07db1154d5b9411004d33cfe5d6a0e842cf15163
permissions -rw-r--r--
Bug 1461243 - Part 6: Stub out obsolete NPAPI APIs _getJavaEnv and _getJavaPeer. r=jimm MozReview-Commit-ID: JkroiRAqzqg

# 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 1454912 - Changed out GENERATED_FILES are handled in the RecursiveMake backend