CLOBBER
author Michael Layzell <michael@thelayzells.com>
Wed, 07 Jun 2017 14:36:46 -0400
changeset 412899 8dd7bd8a399a1d21cad7361765b8c85947b49be5
parent 412410 cbb06ea384e95b8e33886c0825bee14867a8851b
child 415360 c4de7d62221d6aef53809519fee7a30973e5878f
permissions -rw-r--r--
Bug 1369627 - Part 2: Send DimensionInfo down to the content process synchronously when creating a new window, r=smaug MozReview-Commit-ID: GlzJ491RLUE

# 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 1341285: From experience, due to all the build changes in a webrtc.org landing make a clobber usually necessary