CLOBBER
author Daniel Holbert <dholbert@cs.stanford.edu>
Thu, 10 Oct 2013 15:02:49 -0700
changeset 164220 1a9233d029191015a71024344d24089565e07eb4
parent 164119 4275b265451268af7f64845a8a58e881bcbad3e4
child 164247 bf3aa9efc6480e2d2ddc2dbb0a713e1c2d25da33
permissions -rw-r--r--
Bug 922461 followup, to touch CLOBBER file and get code regenerated & avoid running afoul of bug 925243's FAIL_ON_WARNINGS annotation.

# 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/
#

Bug 922461 needs a clobber to regenerate code and survive bug 925243's FAIL_ON_WARNINGS annotation.