CLOBBER
author Oleg Romashin <oleg.romashin@microsoft.com>
Mon, 18 Nov 2013 13:10:05 -0800
changeset 170753 a5e360e6d7138308bf6e7e3fe1e987960a4c7da7
parent 170574 677200e185c24cfc35029728ed4072c4c8ec7462
child 170576 c913eeee3dfcd7908915756ed841d09e35d4e7a7
child 170973 ddf925dab8617170c22d558de5c11fa3e1a5e167
permissions -rw-r--r--
Bug 822898 - Implement pointer events. Interface. r=smaug

# 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/
#

Australis landing.