CLOBBER
author Ehsan Akhgari <ehsan@mozilla.com>
Tue, 01 Aug 2017 19:50:50 -0400
changeset 424733 17155d1c2ca71ef2e3a21254f4dbeae52a0b99e8
parent 424206 52285ea5e54c73d3ed824544cef2ee3f195f05e6
child 425542 704c58d8803e7a0388111af34325dc1964cd4a3b
permissions -rw-r--r--
Bug 1386411 - Part 6: Add a more efficient nsISelectionController::GetSelection() API for retrieving native Selection objects; r=bzbarsky This API avoids needless refcounting and QueryInterface overhead.

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

Merge day clobber