Update to NSPR 4.10.8

README.chromium

Index: README.chromium
diff --git a/README.chromium b/README.chromium
index 50656f5f7be06c4c227a1e6aff3b9ecf28f60a17..4aa56b59e5623a77a82f5c51a291f8b2b665edfc 100644
--- a/README.chromium
+++ b/README.chromium
@@ -7,7 +7,7 @@ License File: nss/COPYING
 Security Critical: yes
 
 Description:
-NSS 3.16.5 with NSPR 4.10.7
+NSS 3.16.5 with NSPR 4.10.8
 
 This copy of NSS has been customized for Chromium.  NSPR is also put here
 rather than in a separate directory to emphasize the fact that Chromium is
@@ -22,7 +22,7 @@ Linux.
 The source code was checked out from the mozilla.org CVS or hg repository using
 the nspr-checkout.sh and nss-checkout.sh scripts in the scripts directory.
 The current source code was checked out with the hg tag NSS_3_16_5_RTM
-and the hg tag NSPR_4_10_7_RTM.
+and the hg tag NSPR_4_10_8_RTM.
 
 Local Modifications:
 
@@ -36,9 +36,6 @@ We made the following local changes to NSPR.
   (The "system" vs. "user" thread distinction comes from Java, and
   ultimately from Solaris threads.)  This is a workaround for
   http://crbug.com/40663.
-- patches/nspr-no-pointers-in-longs.patch Don't store pointers in longs.
-  Pointers can be 64-bit, and longs are only 32-bit on Windows. See
-  https://bugzilla.mozilla.org/show_bug.cgi?id=1105144
 - patches/nspr-remove-io.patch: Remove IO operations in NSPR to allow NSS
   to work in the sandbox.  Do not initialize IO when initializing NSPR.
   Windows version of NSPR also tried to use getaddrinfo to resolve hostname