Author: dlester
Date: Wed Aug 5 07:17:12 2015
New Revision: 1694139
URL: http://svn.apache.org/r1694139
Log:
Update documentation.
Modified:
mesos/site/publish/documentation/fetcher-cache-internals/index.html
mesos/site/publish/documentation/latest/fetcher-cache-internals/index.html
mesos/site/publish/documentation/latest/submitting-a-patch/index.html
mesos/site/publish/documentation/submitting-a-patch/index.html
mesos/site/publish/sitemap.xml
mesos/site/source/documentation/latest/fetcher-cache-internals.md
mesos/site/source/documentation/latest/submitting-a-patch.md
Modified: mesos/site/publish/documentation/fetcher-cache-internals/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/fetcher-cache-internals/index.html?rev=1694139&r1=1694138&r2=1694139&view=diff
==============================================================================
--- mesos/site/publish/documentation/fetcher-cache-internals/index.html
(original)
+++ mesos/site/publish/documentation/fetcher-cache-internals/index.html Wed Aug
5 07:17:12 2015
@@ -192,7 +192,7 @@
<p>The resources named “A” and “B” have been fetched
with caching into sandbox 1 and 2 below. In the course of this, two cache
entries have been created and two files have been downloaded into the cache and
named “1” and “2”. (Cache file names have unique names
that comprise serial numbers.)</p>
-<p>The next figure illustrates the state after fetching a different cached URI
into sandbox 3, which in this case requires evicting a cache-resident file and
its entry. Steps:
+<p>The next figure illustrates the state after fetching a different cached URI
into sandbox 3, which in this case requires evicting a cache-resident file and
its entry. Cache eviction removes cache entries in the order of the least
recently used cache entries. Steps if “A” was fetched before
“B”:
1. Remove the cache entry for “A” from the fetcher process' cache
entry table. Its faded depiction is supposed to indicate this. This immediately
makes it appear as if the URI has never been cached, even though the cache file
is still around.
2. Proceed with fetching “C”. This creates a new cache file, which
has a different unique name. (The fetcher process remembers in its cache entry
which file name belongs to which URI.)</p>
Modified:
mesos/site/publish/documentation/latest/fetcher-cache-internals/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/fetcher-cache-internals/index.html?rev=1694139&r1=1694138&r2=1694139&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/fetcher-cache-internals/index.html
(original)
+++ mesos/site/publish/documentation/latest/fetcher-cache-internals/index.html
Wed Aug 5 07:17:12 2015
@@ -192,7 +192,7 @@
<p>The resources named “A” and “B” have been fetched
with caching into sandbox 1 and 2 below. In the course of this, two cache
entries have been created and two files have been downloaded into the cache and
named “1” and “2”. (Cache file names have unique names
that comprise serial numbers.)</p>
-<p>The next figure illustrates the state after fetching a different cached URI
into sandbox 3, which in this case requires evicting a cache-resident file and
its entry. Steps:
+<p>The next figure illustrates the state after fetching a different cached URI
into sandbox 3, which in this case requires evicting a cache-resident file and
its entry. Cache eviction removes cache entries in the order of the least
recently used cache entries. Steps if “A” was fetched before
“B”:
1. Remove the cache entry for “A” from the fetcher process' cache
entry table. Its faded depiction is supposed to indicate this. This immediately
makes it appear as if the URI has never been cached, even though the cache file
is still around.
2. Proceed with fetching “C”. This creates a new cache file, which
has a different unique name. (The fetcher process remembers in its cache entry
which file name belongs to which URI.)</p>
Modified: mesos/site/publish/documentation/latest/submitting-a-patch/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/submitting-a-patch/index.html?rev=1694139&r1=1694138&r2=1694139&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/submitting-a-patch/index.html
(original)
+++ mesos/site/publish/documentation/latest/submitting-a-patch/index.html Wed
Aug 5 07:17:12 2015
@@ -115,6 +115,7 @@
<ol>
<li>Before beginning, please read the <a
href="/documentation/latest/mesos-c++-style-guide/">Mesos C++ Style Guide</a>.
It is recommended to use the git pre-commit hook
(<code>support/hooks/pre-commit</code>) to automatically check for style
errors. See the hook script for instructions to enable it.</li>
<li>Most of your changes will probably be to files inside of
<code>BASE_MESOS_DIR</code></li>
+<li>From inside of the root Mesos directory: <code>./bootstrap</code> (Only
required if building from git repository).</li>
<li>To build, we recommend that you don’t build inside of the src
directory. We recommend you do the following:
<ol>
Modified: mesos/site/publish/documentation/submitting-a-patch/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/submitting-a-patch/index.html?rev=1694139&r1=1694138&r2=1694139&view=diff
==============================================================================
--- mesos/site/publish/documentation/submitting-a-patch/index.html (original)
+++ mesos/site/publish/documentation/submitting-a-patch/index.html Wed Aug 5
07:17:12 2015
@@ -115,6 +115,7 @@
<ol>
<li>Before beginning, please read the <a
href="/documentation/latest/mesos-c++-style-guide/">Mesos C++ Style Guide</a>.
It is recommended to use the git pre-commit hook
(<code>support/hooks/pre-commit</code>) to automatically check for style
errors. See the hook script for instructions to enable it.</li>
<li>Most of your changes will probably be to files inside of
<code>BASE_MESOS_DIR</code></li>
+<li>From inside of the root Mesos directory: <code>./bootstrap</code> (Only
required if building from git repository).</li>
<li>To build, we recommend that you don’t build inside of the src
directory. We recommend you do the following:
<ol>
