2014-05-01 15:55:31 +00:00
|
|
|
# To trigger a clobber replace ALL of the textual description below,
|
2012-03-13 17:00:24 +00:00
|
|
|
# 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 11:14:40 +00:00
|
|
|
# Modifying this file will now automatically clobber the buildbot machines \o/
|
2013-03-18 23:49:25 +00:00
|
|
|
#
|
2013-08-01 01:15:24 +00:00
|
|
|
|
2013-12-12 07:26:38 +00:00
|
|
|
# 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.
|
2013-12-12 21:10:54 +00:00
|
|
|
|
2016-01-25 03:33:52 +00:00
|
|
|
Bug 1237983 - Investigate and remove the Bagheera Client implementation.
|
2016-01-19 23:34:22 +00:00
|
|
|
|