Author: dsahlberg
Date: Wed May  4 21:13:22 2022
New Revision: 1900565

URL: http://svn.apache.org/viewvc?rev=1900565&view=rev
Log:
In site/staging:
* docs/community-guide/releasing.part.html
  (#backport-merge-bot): The machine is svn-qavm2. It was not possible to 
    rename it. See mail in private@
    https://lists.apache.org/thread/qb4v1pzynvbxwc1mkqhk7fnc9br4b3ql

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

Modified: subversion/site/staging/docs/community-guide/releasing.part.html
URL: 
http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/releasing.part.html?rev=1900565&r1=1900564&r2=1900565&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/releasing.part.html (original)
+++ subversion/site/staging/docs/community-guide/releasing.part.html Wed May  4 
21:13:22 2022
@@ -1635,7 +1635,7 @@ using release.py to automate most of the
   <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" 
-->#backport-merge-bot"
     title="Link to this section">&para;</a>
 </h3>
-<p>The backport merge bot runs nightly on the <tt>svn-qavm</tt> machine,
+<p>The backport merge bot runs nightly on the <tt>svn-qavm2</tt> machine,
    under the <tt>svnsvn</tt> local user account, making commits
    using the <tt>svn-role</tt> Subversion account name.  </p>
 <p>This configuration currently requires someone with admin access to
@@ -1663,7 +1663,7 @@ sudo -H -u svnsvn  svn up ~svnsvn/src/sv
 <pre>
 sudo -H -u svnsvn  svn up -r0 ~svnsvn/src/svn/Z.Z.x
 </pre>
-<p>More notes on the setup can be found in <tt>machines/svn-qavm/</tt> and
+<p>More notes on the setup can be found in <tt>machines/svn-qavm2/</tt> and
    in the Subversion PMC's
    <a href="https://svn.apache.org/repos/private/pmc/subversion";>
    private repository</a>. There are also historical notes on previous


Reply via email to