CLOBBER
author Benjamin Smedberg <benjamin@smedbergs.us>
Fri, 20 Jan 2017 14:13:57 -0500
changeset 330777 cade3cd4cc6fb6ba8b4a78def030caf91389b0f3
parent 330694 5a4412474c63e1d9e66036d603ac42e9cb2b9150
child 332444 d8dd09d7df1dc97677499f08f3b99737b4821660
child 342216 b86ff4066687c7f880598820360b3c564b4f60d6
permissions -rw-r--r--
Bug 1332631 part D - file moves from xpcom/glue to xpcom/threads, r=froydnj MozReview-Commit-ID: kDBGvlYjyW

# 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