svn commit: r1867777 - /subversion/site/publish/docs/community-guide/releasing.part.html

[danielsh]

Author: danielsh
Date: Mon Sep 30 14:19:53 2019
New Revision: 1867777

URL: http://svn.apache.org/viewvc?rev=1867777&view=rev
Log:
* docs/community-guide/releasing.part.html
  (#backport-merge-bot): Link to the relevant bug.

Modified:
    subversion/site/publish/docs/community-guide/releasing.part.html

Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL: 
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=1867777&r1=1867776&r2=1867777&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Mon Sep 30 
14:19:53 2019
@@ -1529,7 +1529,8 @@ svn up ~svnsvn/src/svn/<i>A.B.x</i>  # f
 </pre>
 <p>The repo URL is <tt>svn-master.a.o</tt> because the backports merger runs
    <tt>svn ci &amp;&amp; svn up</tt> in a loop, and assumes <tt>svn up</tt> 
will
-   update it to the revision it just committed.  That's not guaranteed
+   update it to the revision it just committed.  That's <a href="/issue4761"
+   >not guaranteed</a>
    when updating from a mirror (and <tt>svn.a.o</tt> may point to a
    mirror).  The buildbot slaves do this too, for the same reason.</p>
 <p>Each branch is in a subdirectory of the WC root.  To add a new