CLOBBER
author tbirdbld
Sat, 19 Aug 2017 15:31:29 -0400
branchTHUNDERBIRD560b3_2017081915_RELBRANCH
changeset 421257 7ff109dc4607024990e15af24b8286ba96f3d416
parent 420956 86913f512c3cda5b2ec612476ea04a370bb3b686
child 423067 704c58d8803e7a0388111af34325dc1964cd4a3b
permissions -rw-r--r--
Added THUNDERBIRD_56_0b3_RELEASE THUNDERBIRD_56_0b3_BUILD1 tag(s) for changeset 126b591ebd3e. DONTBUILD CLOSED TREE a=release

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

Merge day clobber