CLOBBER
author Cameron McCormack <cam@mcc.id.au>
Mon, 13 Apr 2015 12:34:15 +1000
changeset 256003 0d51d7946a032369086869c600f49aa3d25f0b20
parent 255662 4516357fdf7a9890d7f2c444df76bf787938d605
child 255946 81c108144278261d7e2eefefe7b044202b7f1fab
permissions -rw-r--r--
Bug 1153693 - Only call ReleaseRef on nsStyle{ClipPath,Filter} once when setting a new value. r=dbaron

# 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 1146355: Run Bluetooth APIs v1 and v2 with same backend code