CLOBBER
author Trevor Saunders <tbsaunde@tbsaunde.org>
Tue, 06 Oct 2015 14:00:20 -0400
changeset 301905 605191307c3a7530db1172f51039c5bee01499c1
parent 301524 d823b6f2f8d27f287f21f14ce14f44ba20b06395
child 301969 6bc7d5fb5686ba81830ea0b8ab50590b7b97b324
permissions -rw-r--r--
bug 1209615 - add RootAccessible::GetPrimaryRemoteTopLevelContentDoc() r=davidb

# 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 1193206 - Building with Android support library 23.0.1