author Noemi Erli <>
Mon, 01 Oct 2018 15:56:26 +0300
changeset 497401 bca1787fc4d346e9452e2a88d14e8fdc7945695c
parent 493008 bade35bc346f3bc1f5e8b59d3d49c7a1ba28166c
child 498071 be74e0c5c16433b1d7d2cba53565f8b7f6681700
permissions -rw-r--r--
Backed out 4 changesets (bug 1488507, bug 1494170) for failures in browser/base/content/test/static/browser_all_files_referenced.js CLOSED TREE Backed out changeset 51b6727d7abd (bug 1488507) Backed out changeset 8887f8ebc376 (bug 1494170) Backed out changeset fc1300333ea2 (bug 1494170) Backed out changeset c9b20f40041d (bug 1494170)

# 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