Commit 1abd61ed authored by mseaborn@chromium.org's avatar mseaborn@chromium.org

NaCl: Update revision in DEPS, r10001 -> r10012

This pulls in the following Native Client changes:

r10002: (mseaborn) Attempt to fix flakiness in run_multidomain_test's exit status on Windows
r10003: (mseaborn) service_runtime: Move TLS values to live exclusively in NaClThreadContext
r10004: (bradnelson) Enhancing HttpDownload to support absent resources and logging.
r10005: (noelallen) Assume missing timestamp (file) is stale.
r10006: (phosek) Generic containers moved into a separate module, split each container into individual source file.
r10007: (petarj) [MIPS] New pattern in validator to detect jumps/branches in delay slots.
r10008: (shcherbina) Validator testing: split some huge tests into parts.
r10009: (petarj) [MIPS] Update SConstruct to use new MIPS toolchain.
r10010: (khim) Bump REVISIONS
r10011: (dschuff) Fix GYP generator export in pnacl buildbot script
r10012: (dschuff) PNaCL merge script: fix upstream remote setup and get up to date HEAD

BUG=none
TEST=nacl_integration

Review URL: https://codereview.chromium.org/11189004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@162270 0039d316-1c4b-4281-b951-d872f2087c98
parent 4c2dee23
...@@ -12,7 +12,7 @@ vars = { ...@@ -12,7 +12,7 @@ vars = {
"chromium_git": "http://git.chromium.org/git", "chromium_git": "http://git.chromium.org/git",
"chromiumos_git": "http://git.chromium.org/chromiumos", "chromiumos_git": "http://git.chromium.org/chromiumos",
"swig_revision": "69281", "swig_revision": "69281",
"nacl_revision": "10001", "nacl_revision": "10012",
# After changing nacl_revision, run 'glient sync' and check native_client/DEPS # After changing nacl_revision, run 'glient sync' and check native_client/DEPS
# to update other nacl_*_revision's. # to update other nacl_*_revision's.
"nacl_tools_revision": "9330", # native_client/DEPS: tools_rev "nacl_tools_revision": "9330", # native_client/DEPS: tools_rev
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment