CLOBBER
author Andreas Tolfsen <ato@sny.no>
Mon, 19 Jun 2017 13:14:44 +0100
changeset 378672 18f262edae6fc63d5a206601f52bfb04a2de5214
parent 378467 5cc81a8efe158d3ea9504251cb3563d1a474e4b6
child 380999 3b514f20525296a9b6a623ba680fb027bc9e6cae
permissions -rw-r--r--
webdriver: cargo: release 0.27.0 Source-Repo: https://github.com/mozilla/webdriver-rust Source-Revision: 1b8863b569ef6efe5f20f7a084e5910f1280285f

# 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 1395486 - Moving files to content-accessible requires a clobber so as not to break Android packaging.