Modified: mesos/site/source/documentation/latest/fetcher-cache-internals.md
URL: 
http://svn.apache.org/viewvc/mesos/site/source/documentation/latest/fetcher-cache-internals.md?rev=1694139&r1=1694138&r2=1694139&view=diff
==============================================================================
--- mesos/site/source/documentation/latest/fetcher-cache-internals.md (original)
+++ mesos/site/source/documentation/latest/fetcher-cache-internals.md Wed Aug  
5 07:17:12 2015
@@ -104,7 +104,7 @@ Besides, everything touched in 1/a and 1
 
 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.)
 
-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:
+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.)
 

Modified: mesos/site/source/documentation/latest/submitting-a-patch.md
URL: 
http://svn.apache.org/viewvc/mesos/site/source/documentation/latest/submitting-a-patch.md?rev=1694139&r1=1694138&r2=1694139&view=diff
==============================================================================
--- mesos/site/source/documentation/latest/submitting-a-patch.md (original)
+++ mesos/site/source/documentation/latest/submitting-a-patch.md Wed Aug  5 
07:17:12 2015
@@ -27,7 +27,8 @@ layout: documentation
 7. Make your changes to the code (using whatever IDE/editor you choose) to 
actually fix the bug or implement the feature.
     1. Before beginning, please read the [Mesos C++ Style 
Guide](/documentation/latest/mesos-c++-style-guide/). It is recommended to use 
the git pre-commit hook (`support/hooks/pre-commit`) to automatically check for 
style errors. See the hook script for instructions to enable it.
     2. Most of your changes will probably be to files inside of 
`BASE_MESOS_DIR`
-    3. To build, we recommend that you don't build inside of the src 
directory. We recommend you do the following:
+    3. From inside of the root Mesos directory: `./bootstrap` (Only required 
if building from git repository).
+    4. To build, we recommend that you don't build inside of the src 
directory. We recommend you do the following:
         1. From inside of the root Mesos directory: `mkdir build && cd build`
         2. `../configure`
         3. `make`


Reply via email to