CLOBBER
author Cameron McCormack <cam@mcc.id.au>
Mon, 13 Jan 2014 14:14:35 +1100
changeset 167354 93d20eba2597f73741593a7614079efe3be7f671
parent 167094 37516445a0b58a662a5fcd8734db0b1c8b633be9
child 167257 e6fc7735a592c666ccf6fa47e93d055d6f81d663
permissions -rw-r--r--
Improve a comment in .lldbinit; no bug. (DONTBUILD)

# 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 944533 requires clobber to force a Proguard refresh