CLOBBER
author JW Wang <jwwang@mozilla.com>
Mon, 21 Jul 2014 18:26:03 -0700
changeset 229203 68e087b509e067ebc6d7acaf3da57b1a780a3b31
parent 229200 428d4d3c8588d8f3ba60dc9026b528c13645d29a
child 195525 4d5d939010e5ace0bdcfc5968e3b3e5788e2dc38
child 229515 83411dedecb455b1ce5debaa6338beda5f1cb5da
permissions -rw-r--r--
Bug 1037370 - Fix null exception for parentNode becomes null when the last token is finished. r=cajbir, a=test-only

# 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