commit fd0e41aac417defff2ddc14cf48de53223e06397
author Yue Gan <yueg@google.com> Thu Nov 24 10:58:17 2016 +0000
committer Dmitry Lomov <dslomov@google.com> Thu Nov 24 13:33:27 2016 +0000
tree c63f207e9c69738228bc5bf31a4730f9f65807e3
parent 460db0f9487197754b8eaf66fb0c8da2bd7799f7

Updates sandbox doc. Fixes #2112.

--
MOS_MIGRATED_REVID=140119096

site/versions/master/docs/bazel-user-manual.html

diff --git a/site/versions/master/docs/bazel-user-manual.html b/site/versions/master/docs/bazel-user-manual.html
index baa9800..8cba504 100644
--- a/site/versions/master/docs/bazel-user-manual.html
+++ b/site/versions/master/docs/bazel-user-manual.html
@@ -839,7 +839,7 @@
   Bazel uses sandboxes to guarantee that actions run hermetically<sup>1</sup> and correctly.
   Bazel runs <i>Spawn</i>s (loosely speaking: actions) in sandboxes that only contain the minimal
   set of files the tool requires to do its job. Currently sandboxing works on Linux 3.12 or newer
-  with the <code>CONFIG_USER_NS</code> option enabled.
+  with the <code>CONFIG_USER_NS</code> option enabled, and also on Mac OS 10.11 for newer.
 </p>
 <p>
   Bazel will print a warning if your system does not support sandboxing to alert you to the fact