svn commit: r1905965 - /subversion/site/staging/docs/release-notes/1.15.html

[ha...@apache.org]

Author: hartmannathan
Date: Tue Dec 13 14:21:46 2022
New Revision: 1905965

URL: http://svn.apache.org/viewvc?rev=1905965&view=rev
Log:
In site/staging: Document that Pristines On Demand is (currently) per-wc

* site/staging/docs/release-notes/1.15.html:
  (#pristines-on-demand): As above. Also, add "Limitations and Future
   Possibilities" to document the possibility for more granular control in a
   future release.

Modified:
    subversion/site/staging/docs/release-notes/1.15.html

Modified: subversion/site/staging/docs/release-notes/1.15.html
URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.15.html?rev=1905965&r1=1905964&r2=1905965&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/1.15.html (original)
+++ subversion/site/staging/docs/release-notes/1.15.html Tue Dec 13 14:21:46 2022
@@ -230,7 +230,7 @@ pristines all the time. Some example use
 </ul>
 
 <p>As of Subversion 1.15, users can opt for Pristines On Demand at checkout
-time:</p>
+time. This applies to the entire working copy:</p>
 
 <pre>
 $ svn checkout --store-pristine=no $REPO $WC
@@ -345,6 +345,15 @@ properties.) Just as <tt>svn status</tt>
 column for such differences, neither will these cause the pristine to be
 downloaded from the repository.</p>
 
+<p>Limitations and Future Possibilities:</p>
+
+<p>Currently, this feature applies to an entire working copy. That is, either
+all working files have their pristines cached (the default) or all working
+files use pristines on demand (<tt>--store-pristine=no</tt>). In the future,
+this feature may be enhanced to give users more granular control, such as by
+allowing the <tt>--store-pristine</tt> switch to apply to individual files.
+</p>
+
 </div> <!-- pristines-on-demand -->
 
 <div class="h3" id="streamy-checkouts">