CLOBBER
author Ed Morley <emorley@mozilla.com>
Wed, 21 Aug 2013 12:59:33 +0100
changeset 143661 ba6c02fc1fe65230f289ca9eeed9c42af3edde6a
parent 143646 0b13d1bd2e732bba957674e5567766bd0597ece2
parent 143546 b35d078803e4d1ad12a146d844c6738d9f7e875f
child 143823 11f66b4a00ed9b81ec31236e64f7e26feb263d3e
permissions -rw-r--r--
Merge latest green inbound changeset and mozilla-central

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

In Bug 863306 comment #42 sheriff KWierso states that we should CLOBBER every time
that WebRTC code is changed, which will be awesome.