CLOBBER
author Benjamin Smedberg <benjamin@smedbergs.us>
Thu, 09 Feb 2017 11:53:50 -0500
changeset 344824 6a7996fa2e1b842d363ceb68aba80e9ee94ef28e
parent 344093 a180b976c165b6cd174d24bbb77941919cdc53cb
child 345340 af1edb14a70783428bd19329869bd06e6ae74b44
permissions -rw-r--r--
Bug 1338172 part E - make all the PPluginWidget stuff Windows-only. Rip out the GTK-specific native widget support from widget/gtk/nsWindow and elsewhere, r=jimm MozReview-Commit-ID: J6E8sYcyX4U

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

Touching clobber for Telemetry IPC refactor in bug 1339749.