CLOBBER
author Yati Sagade <yati.sagade@gmail.com>
Wed, 27 Feb 2013 22:30:56 +0530
changeset 133841 8f83edc05fa4d458d82668a95853c907544d0b8d
parent 133745 c65d59d33aa86b7e75bc420ea3beda6201e0aceb
child 133999 231b7f8046d9a610a7840d5bee7cc4abe99ddb12
permissions -rw-r--r--
Bug 812179 - Removed hacks for Python < 2.6 from config/ [r=ted]

# 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.
#
Bug 784841 pretty much changed how the build system works. It's best to clobber.