CLOBBER
author Wes Kocher <wkocher@mozilla.com>
Mon, 11 May 2015 14:54:02 -0700
changeset 243425 86efbb9287a4cdb68908aa9322ef45008394d349
parent 242521 60349cbc3d4eb0423b20303a7c4384d9f715a133
child 243221 502e1a5e722f10b2fd53db0c8bfccef239dd3ef9
permissions -rw-r--r--
Backed out 2 changesets (bug 1159401) for b2g build bustage Backed out changeset adfee1efb1e1 (bug 1159401) Backed out changeset 70c63c8546e3 (bug 1159401)

# 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 1155494 seems to need a clobber to pick up a change the ipdl parser.