CLOBBER
author Masayuki Nakano <masayuki@d-toybox.com>
Wed, 16 Mar 2016 13:47:50 +0900
changeset 288908 c0f93cbdbc17f7ea0b8b533f6e0d93845bef96c0
parent 288739 e2974ac0c94f60d020a7679c18f17a9b918b4ce1
child 290265 559a80645f20706e1eaaeed863e90c2d35ff7644
permissions -rw-r--r--
Bug 1137563 part.4 Implement IMEInputHandler::WillDispatchKeyboardEvent() r=m_kato

# 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 1223729 - Touching CLOBBER for moving files under dom/bluetooth/common