CLOBBER
author Jeff Muizelaar <jmuizelaar@mozilla.com>
Wed, 16 Dec 2015 16:14:37 -0500
changeset 298053 5900cd9ccb59b222a03f14c7673edaf7d5afbd9a
parent 297966 e2031358e2a6d6d686b7a6b592d07cfb874bacae
child 298713 31a4f341fc38ee9f855a8b0882722757c6847bb5
permissions -rw-r--r--
Bug 1232462. Only ask for a higher version of GLSL when using WebGL2. r=jgilbert a=sylvestre This fixes the situation for now. I'm going to try to work out what should actually be happening here with ANGLE. See also: https://bugs.chromium.org/p/angleproject/issues/detail?id=1256

# 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