You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by bu...@apache.org on 2019/01/04 17:12:01 UTC

svn commit: r1038533 - in /websites/staging/httpd/trunk/content: ./ dev/devnotes.html

Author: buildbot
Date: Fri Jan  4 17:12:01 2019
New Revision: 1038533

Log:
Staging update by buildbot for httpd

Modified:
    websites/staging/httpd/trunk/content/   (props changed)
    websites/staging/httpd/trunk/content/dev/devnotes.html

Propchange: websites/staging/httpd/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan  4 17:12:01 2019
@@ -1 +1 @@
-1850103
+1850406

Modified: websites/staging/httpd/trunk/content/dev/devnotes.html
==============================================================================
--- websites/staging/httpd/trunk/content/dev/devnotes.html (original)
+++ websites/staging/httpd/trunk/content/dev/devnotes.html Fri Jan  4 17:12:01 2019
@@ -145,7 +145,7 @@ called <samp>httpd-trunk</samp>:</li>
  httpd-trunk</samp></dd>
 </dl>
 <p>This step only needs to be performed once (unless the private working
-directory is tainted or deleted.) Committers should use a URL prefix
+directory is tainted or deleted). Committers should use a URL prefix
 of <samp>https</samp> on the checkout, to save themselves headaches later.</p>
 <ol>
 <li>Developer keeps their working directory synchronised with changes made to
@@ -180,23 +180,23 @@ developer checks the changes into the re
 the Apache SVN repository that pertain to the different releases. The top
 level can be perused with the <a href="http://svn.apache.org/viewcvs.cgi/">SVN
 ViewCVS</a> pages. The main subtrees
-pertaining to the <samp>httpd</samp>server source are:</p>
+pertaining to the <samp>httpd</samp> server source are:</p>
 <h2 id="httpd-24">httpd-2.4<a class="headerlink" href="#httpd-24" title="Permanent link">&para;</a></h2>
 <p>To create a directory tree containing the 2.4 sources, and call
 it <samp>httpd-2.4</samp>, change your current directory to the <em>parent</em> of
 the tree and then check the 2.4 sources out as follows:
 <pre>
 % cd /usr/local/apache
-% svn checkout http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x
-   httpd-2.4</pre></p>
+% svn checkout http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x httpd-2.4
+</pre></p>
 <h2 id="httpd-25">httpd-2.5<a class="headerlink" href="#httpd-25" title="Permanent link">&para;</a></h2>
 <p>If you want to check out the bleeding edge of development, the httpd-2.5
 development tree (slated for a release 2.6), and call
 it <samp>httpd-trunk</samp>, checkout as follows:
 <pre>
 % cd /usr/local/apache
-% svn checkout http://svn.apache.org/repos/asf/httpd/httpd/trunk
-httpd-trunk</pre></p>
+% svn checkout http://svn.apache.org/repos/asf/httpd/httpd/trunk httpd-trunk
+</pre></p>
 <h2 id="httpd-site">httpd-site<a class="headerlink" href="#httpd-site" title="Permanent link">&para;</a></h2>
 <p>This subtree contains the files that live
 at <samp>http://httpd.apache.org/</samp>. The directory on the host that
@@ -212,7 +212,7 @@ is <samp>https://svn.apache.org/repos/as
 <make_note>It is important that the files on the Web host not be modified
 directly. If you want or need to change one, check it out into a private
 working copy, modify <strong>that</strong> , commit the change into SVN, and then
-perform a <samp>svn update</samp>to bring the host directory into sync with
+perform a <samp>svn update</samp> to bring the host directory into sync with
 the SVN sources.</make_note>
 The Web site <em>directories</em> (as opposed to files) are not maintained in
 synch with the SVN files automatically. They are manually updated from SVN
@@ -220,7 +220,7 @@ by various people as they consider appro
 issue, unless a group of files are being updated according to an ongoing
 group discussion.</p>
 <h2 id="httpd-dist">httpd-dist<a class="headerlink" href="#httpd-dist" title="Permanent link">&para;</a></h2>
-<p>Like the <samp>httpd-site</samp>subtree, this one is used to maintain the
+<p>Like the <samp>httpd-site</samp> subtree, this one is used to maintain the
 files that comprise a website - in this
 case, <samp>http://www.apache.org/dist/httpd/</samp>. Also like the previous
 subtree, the directory on the server is a checked-out working copy of this
@@ -232,8 +232,8 @@ is <samp>https://svn.apache.org/repos/as
 <p>Committers will generally deal with this subtree when "rolling" a release.
 This is a series of steps taken to create a complete new release of the
 Apache httpd software. Amongst other things, the key to this subtree is
-the <samp>tools/</samp>directory, which contains
-the <samp>release.sh</samp>shell script. More information on the policies
+the <samp>tools/</samp> directory, which contains
+the <samp>release.sh</samp> shell script. More information on the policies
 and procedures relating to rolling releases can be found on the <a href="release.html">Release
 Guidelines</a> page.</p>
 <h1 id="setting-up-remote-svn">Setting Up Remote SVN<a class="headerlink" href="#setting-up-remote-svn" title="Permanent link">&para;</a></h1>
@@ -248,10 +248,10 @@ pull requests, but we can comment/review
 commit message can contain the phrase "this closes #X" where X is the 
 pull request number which will be prominent in the interface.</p>
 <ul>
-<li>https://github.com/apache/httpd</li>
-<li>https://github.com/apache/httpd/pulls</li>
+<li><a href="https://github.com/apache/httpd">https://github.com/apache/httpd</a></li>
+<li><a href="https://github.com/apache/httpd/pulls">https://github.com/apache/httpd/pulls</a></li>
 </ul>
-<p>An example revision that closes a pull request is http://svn.apache.org/viewvc?view=revision&amp;revision=1780308</p>
+<p>An example revision that closes a pull request is <a href="http://svn.apache.org/viewvc?view=revision&amp;revision=1780308">http://svn.apache.org/viewvc?view=revision&amp;revision=1780308</a></p>
             
 
             <!-- FOOTER -->