My sense is that users keep asking about and requesting exclusive locks
(reserved checkouts) and that the developers have often responded that
this is a high-priority post-1.0 feature. If that's the case, it seems
appropriate that it should be listed on the front web
page with the other planned post-1.0 features.
I've included a patch to that effect.
-Travis
___________________
* www/index.html: add mention that exclusive locking is planned
post-1.0 feature
Index: index.html
===================================================================
--- index.html (revision 9101)
+++ index.html (working copy)
@@ -141,6 +141,13 @@
<ul>
+<li><strong>Exclusive locking</strong>
+ <p>Occasionally a model of change control where files are
+ explicitly checked out for exclusive editing is most
+ appropriate, particularly with binary files which cannot be
+ merged. CVS calls this reserved checkouts. This feature
+ has high priority for post-1.0 implementation.</p>
+
<li><strong>Better merge support</strong>
<p>Improved support for selective merges from related lines of
development, and for repeated merges. (Currently,
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 18 05:17:29 2004