CLOBBER
author James Graham <james@hoppipolla.co.uk>
Tue, 06 Dec 2016 10:30:34 -1000
changeset 366298 838e1c92ded6fff1e1366c81faab1ed3c41add60
parent 365230 7e29173b1641f54d08c60a64cd9d1b5fbc3bba2f
child 367318 caca7170b92ee7874322eba772c15c9416a5ef5d
child 369459 c5c8bd440978ec31deb66443bc2b17095e4a9fa4
permissions -rw-r--r--
Bug 1257249 - Replace a use of cStringIO with StringIO to avoid a problem with old Python versions. r=Ms2ger, a=test-only MozReview-Commit-ID: D1wkrdaejQB

# 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