CLOBBER
author Gregory Szorc <gps@mozilla.com>
Wed, 01 Jun 2016 17:06:01 -0700
changeset 301526 cec0b6d316a992d47a8ab7bd8f2e961130fae99a
parent 300597 c567db06882e3a2e3396b6a16449522d149c7146
child 301791 a08f7952eebaa20f82c83644ae228e4cc3e46d25
permissions -rw-r--r--
Bug 1277406 - Move `mach mercurial-setup` implementation into bootstrap; r=glandium This begins the consolidation of `mach mercurial-setup` into `mach bootstrap`. The first step is to move the content of the mach_commands.py file into the bootstrapper's. I'm not crazy about adding the sys.path entry for tools/mercurial. I intend to clean this up later. MozReview-Commit-ID: Cq56wPG8sO1

# 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