diff --git a/generated/state/page-cache.txt b/generated/state/page-cache.txt
index 62dd7022..63733aaf 100644
--- a/generated/state/page-cache.txt
+++ b/generated/state/page-cache.txt
@@ -25387,6 +25387,21 @@
 "    <ul>
 "      <li>
 "        <div>
+"          <span class="library"><a href="/libs/atomic/">Atomic</a>:</span>
+"          <ul>
+"            <li>
+"              <div>
+"                Implemented SSE2 and SSE4.1 versions of address lookup algorithm,
+"                which is used in the internal lock pool implementation. This may
+"                improve performance of waiting and notifying operations in heavily
+"                contended cases.
+"              </div>
+"            </li>
+"          </ul>
+"        </div>
+"      </li>
+"      <li>
+"        <div>
 "          <span class="library"><a href="/libs/container/">Container</a>:</span>
 "          <ul>
 "            <li>
@@ -25495,6 +25510,78 @@
 "      </li>
 "      <li>
 "        <div>
+"          <span class="library"><a href="/libs/filesystem/">Filesystem</a>:</span>
+"          <ul>
+"            <li>
+"              <div>
+"                <strong>New:</strong> Added <code><span class="identifier">creation_time</span></code>
+"                operation, which allows to obtain file creation time. (Inspired by
+"                <a href="https://github.com/boostorg/filesystem/pull/134">PR#134</a>)
+"              </div>
+"            </li>
+"            <li>
+"              <div>
+"                The returned value of <code><span class="identifier">last_write_time</span><span class="special">(</span><span class="identifier">p</span><span class="special">,</span> <span class="identifier">ec</span><span class="special">)</span></code> operation in case of failure has
+"                been changed to a minimal value representable by <code><span class="identifier">std</span><span class="special">::</span><span class="identifier">time_t</span></code>
+"                instead of -1.
+"              </div>
+"            </li>
+"            <li>
+"              <div>
+"                The returned value of <code><span class="identifier">hard_link_count</span><span class="special">(</span><span class="identifier">p</span><span class="special">,</span> <span class="identifier">ec</span><span class="special">)</span></code> operation in case of failure has
+"                been changed to <code><span class="keyword">static_cast</span><span class="special">&lt;</span><span class="identifier">uintmax_t</span><span class="special">&gt;(-</span><span class="number">1</span><span class="special">)</span></code> instead of 0.
+"              </div>
+"            </li>
+"            <li>
+"              <div>
+"                On POSIX systems, <code><span class="identifier">file_size</span></code>
+"                will now indicate error code <code><span class="identifier">errc</span><span class="special">::</span><span class="identifier">function_not_supported</span></code>
+"                if the path resolves to a non-regular file. Previously, <code><span class="identifier">errc</span><span class="special">::</span><span class="identifier">operation_not_permitted</span></code> was reported.
+"              </div>
+"            </li>
+"            <li>
+"              <div>
+"                On Linux, many operations now use <code><span class="identifier">statx</span></code>
+"                system call internally, when possible, which allows to reduce the
+"                amount of information queried from the filesystem and potentially
+"                improve performance. The <code><span class="identifier">statx</span></code>
+"                system call was introduced in Linux kernel 4.11.
+"              </div>
+"            </li>
+"            <li>
+"              <div>
+"                Removed <code><span class="keyword">const</span></code>-qualification
+"                from return types of some <code><span class="identifier">path</span></code>
+"                methods. This could prevent move construction and move assignment
+"                at the call site in some cases. (<a href="https://github.com/boostorg/filesystem/issues/160">#160</a>)
+"              </div>
+"            </li>
+"            <li>
+"              <div>
+"                On OpenBSD 4.4 and newer, use <code><span class="identifier">statvfs</span></code>
+"                system call to obtain filesystem space information. (Inspired by
+"                <a href="https://github.com/boostorg/filesystem/pull/162">PR#162</a>)
+"              </div>
+"            </li>
+"          </ul>
+"        </div>
+"      </li>
+"      <li>
+"        <div>
+"          <span class="library"><a href="/libs/gil/">GIL</a>:</span>
+"          <ul>
+"            <li>
+"              <div>
+"                BREAKING: In next release, we are going to drop support for GCC 5.
+"                We may also change the required minimum C++ version from C++11 to
+"                C++14.
+"              </div>
+"            </li>
+"          </ul>
+"        </div>
+"      </li>
+"      <li>
+"        <div>
 "          <span class="library"><a href="/libs/interprocess/">Interprocess</a>:</span>
 "          <ul>
 "            <li>
@@ -25545,6 +25632,48 @@
 "      </li>
 "      <li>
 "        <div>
+"          <span class="library"><a href="/libs/log/">Log</a>:</span>
+"          <ul>
+"            <li>
+"              <div>
+"                Bug fixes:
+"                <ul>
+"                  <li>
+"                    <div>
+"                      Corrected the file counter that would be used in <code><span class="identifier">text_file_backend</span></code> when generating
+"                      the target file name (based on the pattern set by <code><span class="identifier">set_target_file_name_pattern</span></code>
+"                      method) when the log file is rotated. (<a href="https://github.com/boostorg/log/issues/125">#125</a>)
+"                    </div>
+"                  </li>
+"                  <li>
+"                    <div>
+"                      Replaced a volatile version counter in <code><span class="identifier">basic_sink_frontend</span></code>
+"                      with an atomic. (<a href="https://github.com/boostorg/log/issues/128">#128</a>)
+"                    </div>
+"                  </li>
+"                  <li>
+"                    <div>
+"                      In the <code><span class="identifier">asynchronous_sink</span></code>
+"                      frontend, resolved a possible conflict between <code><span class="identifier">flush</span></code> and <code><span class="identifier">run</span></code>
+"                      methods, if <code><span class="identifier">run</span></code>
+"                      is called from a user's thread instead of the internal dedicated
+"                      thread spawned by the frontend. (<a href="https://github.com/boostorg/log/issues/131">#131</a>)
+"                    </div>
+"                  </li>
+"                </ul>
+"              </div>
+"            </li>
+"            <li>
+"              <div>
+"                See <a href="/libs/log/doc/html/log/changelog.html">changelog</a>
+"                for more details.
+"              </div>
+"            </li>
+"          </ul>
+"        </div>
+"      </li>
+"      <li>
+"        <div>
 "          <span class="library"><a href="/libs/move/">Move</a>:</span>
 "          <ul>
 "            <li>
@@ -25817,7 +25946,7 @@
 "  </div>
 "
 -hash
-"f5040628f1eb0a3e7f91de3496efd7d0fd7b0bccc25ff5bc5336cc0f10e81f9c
+"1605b9df261192a63e698d941c4850773e7a65a61a46bb9d507f21ceff9bd0f0
 -id
 "version_1_75_0
 -notice_url
diff --git a/users/history/in_progress.html b/users/history/in_progress.html
index e3cdb296..5b710813 100644
--- a/users/history/in_progress.html
+++ b/users/history/in_progress.html
@@ -65,6 +65,21 @@
   <div id="version_1_75_0.updated_libraries">
     <h3><span class="link">Updated Libraries</span></h3>
     <ul>
+      <li>
+        <div>
+          <span class="library"><a href="/doc/libs/master/libs/atomic/">Atomic</a>:</span>
+          <ul>
+            <li>
+              <div>
+                Implemented SSE2 and SSE4.1 versions of address lookup algorithm,
+                which is used in the internal lock pool implementation. This may
+                improve performance of waiting and notifying operations in heavily
+                contended cases.
+              </div>
+            </li>
+          </ul>
+        </div>
+      </li>
       <li>
         <div>
           <span class="library"><a href="/doc/libs/master/libs/container/">Container</a>:</span>
@@ -173,6 +188,78 @@
           </ul>
         </div>
       </li>
+      <li>
+        <div>
+          <span class="library"><a href="/doc/libs/master/libs/filesystem/">Filesystem</a>:</span>
+          <ul>
+            <li>
+              <div>
+                <strong>New:</strong> Added <code><span class="identifier">creation_time</span></code>
+                operation, which allows to obtain file creation time. (Inspired by
+                <a href="https://github.com/boostorg/filesystem/pull/134">PR#134</a>)
+              </div>
+            </li>
+            <li>
+              <div>
+                The returned value of <code><span class="identifier">last_write_time</span><span class="special">(</span><span class="identifier">p</span><span class="special">,</span> <span class="identifier">ec</span><span class="special">)</span></code> operation in case of failure has
+                been changed to a minimal value representable by <code><span class="identifier">std</span><span class="special">::</span><span class="identifier">time_t</span></code>
+                instead of -1.
+              </div>
+            </li>
+            <li>
+              <div>
+                The returned value of <code><span class="identifier">hard_link_count</span><span class="special">(</span><span class="identifier">p</span><span class="special">,</span> <span class="identifier">ec</span><span class="special">)</span></code> operation in case of failure has
+                been changed to <code><span class="keyword">static_cast</span><span class="special">&lt;</span><span class="identifier">uintmax_t</span><span class="special">&gt;(-</span><span class="number">1</span><span class="special">)</span></code> instead of 0.
+              </div>
+            </li>
+            <li>
+              <div>
+                On POSIX systems, <code><span class="identifier">file_size</span></code>
+                will now indicate error code <code><span class="identifier">errc</span><span class="special">::</span><span class="identifier">function_not_supported</span></code>
+                if the path resolves to a non-regular file. Previously, <code><span class="identifier">errc</span><span class="special">::</span><span class="identifier">operation_not_permitted</span></code> was reported.
+              </div>
+            </li>
+            <li>
+              <div>
+                On Linux, many operations now use <code><span class="identifier">statx</span></code>
+                system call internally, when possible, which allows to reduce the
+                amount of information queried from the filesystem and potentially
+                improve performance. The <code><span class="identifier">statx</span></code>
+                system call was introduced in Linux kernel 4.11.
+              </div>
+            </li>
+            <li>
+              <div>
+                Removed <code><span class="keyword">const</span></code>-qualification
+                from return types of some <code><span class="identifier">path</span></code>
+                methods. This could prevent move construction and move assignment
+                at the call site in some cases. (<a href="https://github.com/boostorg/filesystem/issues/160">#160</a>)
+              </div>
+            </li>
+            <li>
+              <div>
+                On OpenBSD 4.4 and newer, use <code><span class="identifier">statvfs</span></code>
+                system call to obtain filesystem space information. (Inspired by
+                <a href="https://github.com/boostorg/filesystem/pull/162">PR#162</a>)
+              </div>
+            </li>
+          </ul>
+        </div>
+      </li>
+      <li>
+        <div>
+          <span class="library"><a href="/doc/libs/master/libs/gil/">GIL</a>:</span>
+          <ul>
+            <li>
+              <div>
+                BREAKING: In next release, we are going to drop support for GCC 5.
+                We may also change the required minimum C++ version from C++11 to
+                C++14.
+              </div>
+            </li>
+          </ul>
+        </div>
+      </li>
       <li>
         <div>
           <span class="library"><a href="/doc/libs/master/libs/interprocess/">Interprocess</a>:</span>
@@ -223,6 +310,48 @@
           </ul>
         </div>
       </li>
+      <li>
+        <div>
+          <span class="library"><a href="/doc/libs/master/libs/log/">Log</a>:</span>
+          <ul>
+            <li>
+              <div>
+                Bug fixes:
+                <ul>
+                  <li>
+                    <div>
+                      Corrected the file counter that would be used in <code><span class="identifier">text_file_backend</span></code> when generating
+                      the target file name (based on the pattern set by <code><span class="identifier">set_target_file_name_pattern</span></code>
+                      method) when the log file is rotated. (<a href="https://github.com/boostorg/log/issues/125">#125</a>)
+                    </div>
+                  </li>
+                  <li>
+                    <div>
+                      Replaced a volatile version counter in <code><span class="identifier">basic_sink_frontend</span></code>
+                      with an atomic. (<a href="https://github.com/boostorg/log/issues/128">#128</a>)
+                    </div>
+                  </li>
+                  <li>
+                    <div>
+                      In the <code><span class="identifier">asynchronous_sink</span></code>
+                      frontend, resolved a possible conflict between <code><span class="identifier">flush</span></code> and <code><span class="identifier">run</span></code>
+                      methods, if <code><span class="identifier">run</span></code>
+                      is called from a user's thread instead of the internal dedicated
+                      thread spawned by the frontend. (<a href="https://github.com/boostorg/log/issues/131">#131</a>)
+                    </div>
+                  </li>
+                </ul>
+              </div>
+            </li>
+            <li>
+              <div>
+                See <a href="/doc/libs/master/libs/log/doc/html/log/changelog.html">changelog</a>
+                for more details.
+              </div>
+            </li>
+          </ul>
+        </div>
+      </li>
       <li>
         <div>
           <span class="library"><a href="/doc/libs/master/libs/move/">Move</a>:</span>