CLOBBER
author Chris H-C <chutten@mozilla.com>
Mon, 04 Apr 2016 12:54:41 -0400
branchFUNNELCAKE86_BRANCH
changeset 326423 d71f2fa0771913a9bd47265869332a154070673a
parent 326054 dcaf0a6fa115ad73bf7505a8e76464250b971a04
permissions -rw-r--r--
Bug 1260483 - Use AssocQueryString to get friendly protocol handler names. r=jimm In Win8+, AssocQueryString supports ASSOCF_IS_PROTOCOL which simplifies fetching the friendly application name for a given protocol/scheme. For "Universal" apps, this simplified mechanism is required to get something other than TWINUI. MozReview-Commit-ID: pTruoBeTgK

# 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