Author: dsahlberg
Date: Wed May  4 21:16:38 2022
New Revision: 1900566

URL: http://svn.apache.org/viewvc?rev=1900566&view=rev
Log:
Merge 1899393, 1899419, 1899468, 1900565 site/staging

* publish/docs/community-guide/releasing.part.html
  (#backport-merge-bot): Document new svn-qavm2

* publish/docs/community-guide/roles.part.html
  (#partial-commit-access): Fix typo

* publish/docs/release-notes/1.8.html
  (#fsfs-stats): Fix typo

Modified:
    subversion/site/publish/   (props changed)
    subversion/site/publish/docs/community-guide/releasing.part.html
    subversion/site/publish/docs/community-guide/roles.part.html
    subversion/site/publish/docs/release-notes/1.8.html

Propchange: subversion/site/publish/
------------------------------------------------------------------------------
  Merged /subversion/site/staging:r1899393,1899419,1899468,1900565

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=1900566&r1=1900565&r2=1900566&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Wed May  4 
21:16:38 2022
@@ -1631,7 +1631,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
@@ -1659,10 +1659,11 @@ 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><i>[Historical notes can be found in <tt>machines/svn-qavm/</tt> and
-   <tt>machines/svn-qavm2/</tt> in the Subversion PMC's
+<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>.]</i></p>
+   private repository</a>. There are also historical notes on previous
+   incarnations in the history of <tt>machines/</tt>.</p>
 
 </div> <!-- backport-merge-bot -->
 

Modified: subversion/site/publish/docs/community-guide/roles.part.html
URL: 
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/roles.part.html?rev=1900566&r1=1900565&r2=1900566&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/roles.part.html (original)
+++ subversion/site/publish/docs/community-guide/roles.part.html Wed May  4 
21:16:38 2022
@@ -85,7 +85,7 @@ means the full committer has applied sev
 from the proposed partial committer, and realizes things would be
 easier if the person were just committing directly.  It is customary and
 recommended for the sponsor to float the prospect by private@ before
-issueing an invitation, but not required; sponsors are trusted to use
+issuing an invitation, but not required; sponsors are trusted to use
 good judgement.</p>
 
 <p>The sponsor watches the partial committer's first few commits to ensure

Modified: subversion/site/publish/docs/release-notes/1.8.html
URL: 
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.8.html?rev=1900566&r1=1900565&r2=1900566&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Wed May  4 21:16:38 2022
@@ -1458,7 +1458,7 @@ The statistics include:
 <p>Administrators may use this information to decide whether directory
 deltification should be enabled (ratio of directory representation
 vs. file representation sizes) or whether commit policies might to
-be revised (e.g. large .zip files accout for most of the repository).
+be revised (e.g. large .zip files account for most of the repository).
 Some of the data, however, is useful for performance analysis by SVN
 developers only.</p>
 


Reply via email to