CLOBBER
author Gregory Szorc <gps@mozilla.com>
Fri, 27 Oct 2017 14:49:25 -0700
changeset 439807 b676880e0d97b3f00c486c41c09f0da7ad692425
parent 439671 babd400c828aee19ce9416296a1d32deaee3a49a
child 440575 73e0d89a540f1568387efa0e145e7853f9badb10
child 440938 def95432b0a17a1b29bef1e6aea9305d69572fb9
permissions -rw-r--r--
Bug 1412431 - Remove MOZ_UNIFY_BDATE; r=nalexander There are no references to this variable outside client.mk. AFAICT it is unused. The only reasonable justification for retaining this support IMO was Universal MacOS builds. And those are no longer supported. MozReview-Commit-ID: 9MnC18Bd1ge

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

Bug 1163171, Android compiler change