CLOBBER
author Bogdan Tara <btara@mozilla.com>
Mon, 04 Dec 2017 21:58:13 +0200
changeset 394911 715afcd248d8f731e07784eaf065d795b433d41f
parent 393584 172e6c7b3adad03e0ad1467f92ef50a5673a87cb
child 395372 f6b4d071186895efd54fec3c529c86ab4d451395
permissions -rw-r--r--
Backed out 3 changesets (bug 1415670) for failing chrome test dom/grid/test/chrome/test_grid_implicit.html r=backout on a CLOSED TREE Backed out changeset 812aaf31c577 (bug 1415670) Backed out changeset ec9fa6d9dca9 (bug 1415670) Backed out changeset 92d2a5673bbc (bug 1415670)

# 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 1419362 - a11y IDL changes not correctly handled by build system