2012-03-13 10:00:24 -07:00
|
|
|
# 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.
|
|
|
|
|
#
|
2013-04-04 04:14:40 -07:00
|
|
|
# Modifying this file will now automatically clobber the buildbot machines \o/
|
2013-03-18 16:49:25 -07:00
|
|
|
#
|
2013-05-19 13:13:29 -07:00
|
|
|
Bug 549861 backout, on Windows due to bug 873809, tests due to...
|
2013-05-17 10:54:56 -07:00
|
|
|
|
|
|
|
|
Alternative to clobber is to run ./config.status from the objdir and to
|
|
|
|
|
touch the CLOBBER file in the objdir.
|
