diff options
author | James McCoy <jamessan@debian.org> | 2019-01-22 22:41:31 -0500 |
---|---|---|
committer | James McCoy <jamessan@debian.org> | 2019-01-22 22:41:31 -0500 |
commit | 59537652d22f58e0bd3866fa748829676f6156f3 (patch) | |
tree | da083fbc100dc30ce8e4734ae3a8486b96d2f6fd | |
parent | bc8297ba1a5d67b7fa1bc70ed0737174874af0c0 (diff) |
Update release notes
Signed-off-by: James McCoy <jamessan@debian.org>
-rw-r--r-- | debian/svn_1.10_releasenotes.html | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/debian/svn_1.10_releasenotes.html b/debian/svn_1.10_releasenotes.html index aaaeba4..b4af527 100644 --- a/debian/svn_1.10_releasenotes.html +++ b/debian/svn_1.10_releasenotes.html @@ -365,8 +365,8 @@ matching the same name, alias or group and the last match applied:</p> <p>In 1.9 the final, read-only, match for <tt>user</tt>, <tt>&alias</tt> and <tt>@group</tt> would be selected while 1.10 combines all the lines to give read-write access. -The 1.10 implementation may change in future 1.10.x releases, perhaps -to make this case an error.</p> +The 1.10 implementation may change in future releases, perhaps to +<a href="/issue/4794">make this case an error</a>.</p> <p>The 1.9 implementation combined the global and per-repository rules for the same path:</p> @@ -381,9 +381,10 @@ for the same path:</p> <p>In 1.9 this would define access for both <tt>userA</tt> and <tt>userB</tt>, in 1.10 the per-repository rule overrides the global rule and this only defines access for <tt>userB</tt>. The 1.10 -implementation may change in future 1.10.x releases, but the exact -change is still being discussed on the dev mailing list.</p> - +implementation may change in future releases, but the exact change +is still being <a href="/issue/4762">discussed</a> on the dev mailing +list.</p> + </div> <!-- authz-compatibility --> <div class="h4" id="svnadmin-LOCK_PATH-canonical"> |