CLOBBER
author Thomas Zimmermann <tdz@users.sourceforge.net>
Wed, 09 Sep 2015 13:20:57 +0200
changeset 261572 ee015390f701973fdaa46f06f010c2a6ca2198d3
parent 259806 4a8baa5e1cf4bc9dde05a7277dc251621b4dc1e3
child 261349 7364ae67d69e4b0579de19296f354f0fef26335f
permissions -rw-r--r--
Bug 1141616: Lookup service channel in Bluedroid's OPP manager, r=btian Bluedroid's |BluetoothOppManager| now retrieves the OBEX service's channel from the remote device. Previously this was done by the Bluedroid driver internally, but having this functionality in the manager itself will allow for future code sharing with the BlueZ backend.

# 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 1193379 - Moving location of files under dom/bluetooth requires a clobber