author Daniel Varga <>
Wed, 03 Apr 2019 09:04:17 +0300
changeset 467667 eb21297f31590fc47581036327df9779a534875c
parent 464728 891a30b8eee20648df8b62217304fb0a0636349d
child 467938 d10b57a89a73db612a1856bee1975e7cdcbe0e7b
permissions -rw-r--r--
Backed out 2 changesets (bug 1535362) for causing merge conflicts. a=backout Backed out changeset 52636fd2ce17 (bug 1535362) Backed out changeset d363668ebdaa (bug 1535362)

# 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