From: Steven R. Loomis Date: Wed, 6 Feb 2019 00:33:26 +0000 (-0800) Subject: ICU-20395 Fix cldr-icu-readme.txt to not mention whitelist X-Git-Tag: release-64-rc~127 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b6f72c10c903808150fccb2450316e7765dbc100;p=icu ICU-20395 Fix cldr-icu-readme.txt to not mention whitelist --- diff --git a/icu4c/source/data/cldr-icu-readme.txt b/icu4c/source/data/cldr-icu-readme.txt index 717d11962e7..b6f8ebe7bfc 100644 --- a/icu4c/source/data/cldr-icu-readme.txt +++ b/icu4c/source/data/cldr-icu-readme.txt @@ -39,18 +39,14 @@ # #---- # -# IP address whitelisting -# # Parts of the build process (notably building the new ICU data files in step 4) # require http: access to files in the CLDR repository; for example, processing # the files in icu4c/source/data/xml/ may require access to # http://www.unicode.org/repos/cldr/trunk/common/dtd/ldml.dtd # -# Unless you cache the dtds locally by e.g. setting -DCLDR_DTD_CACHE=/tmp, the -# builds will repeatedly make such requests, which will likely result in the -# Unicode server blocking access and consequent timeout failures. You can -# prevent such blockage by having the external IP address of your build system -# whitelisted with Unicode; contact Rick McGowan or Steven Loomis. +# Unless you cache the dtds locally by e.g. setting -DCLDR_DTD_CACHE=/tmp, +# your system will make excessive network requests, which will result in the +# Unicode server blocking access. # #---- #