CLOBBER
author Sylvestre Ledru <sledru@mozilla.com>
Mon, 06 Nov 2017 13:22:06 +0100
changeset 694109 98e2b4ee9775a2a2b5cc1bb8a390bfe901814f38
parent 693188 6eece4a582994d925f1b9bd28a6bd4d1ba467b27
child 695282 afd8cd3488071d127727ede5c0d15047e73e1169
child 695636 78568f0b106895cb7573fb1fa355d511ec9c87a3
child 696531 9e21950bdd34ea547301720d1795d9a1eeba0406
child 696951 6371e71153c8c3d32d31c8eb92ac296f353dd860
permissions -rw-r--r--
reformat all MozReview-Commit-ID: ApY4gI1IbKr

# 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 1413550 - Activity Stream removed a bunch of files that would break ./mach package