humbedooh at apache
Aug 8, 2012, 9:28 AM
Post #1 of 1
(22 views)
Permalink
|
|
svn commit: r1370821 - /httpd/site/trunk/content/dev/devnotes.mdtext
|
|
Author: humbedooh
Date: Wed Aug 8 16:28:14 2012
New Revision: 1370821
URL: http://svn.apache.org/viewvc?rev=1370821&view=rev
Log:
fix whitespace issues
Modified:
httpd/site/trunk/content/dev/devnotes.mdtext
Modified: httpd/site/trunk/content/dev/devnotes.mdtext
URL: http://svn.apache.org/viewvc/httpd/site/trunk/content/dev/devnotes.mdtext?rev=1370821&r1=1370820&r2=1370821&view=diff
==============================================================================
--- httpd/site/trunk/content/dev/devnotes.mdtext (original)
+++ httpd/site/trunk/content/dev/devnotes.mdtext Wed Aug 8 16:28:14 2012
@@ -58,14 +58,14 @@ changes are applied:
1. Developer checks out a copy of the files on which he wants to work (in
this case, the trunk), into a private working directory
-called<samp>httpd-trunk</samp>:
+called <samp>httpd-trunk</samp>:
: <samp>% svn checkout http://svn.apache.org/repos/asf/httpd/httpd/trunk
httpd-trunk</samp>
This step only needs to be performed once (unless the private working
directory is tainted or deleted.) Committers should use a URL prefix
-of<samp>https</samp>on the checkout, to save themselves headaches later.
+of <samp>https</samp> on the checkout, to save themselves headaches later.
1. Developer keeps his working directory synchronised with changes made to
the repository:
@@ -81,7 +81,7 @@ generates a patch so others can apply th
: <samp>% svn diff httpd-trunk/modules/http/mod_mime.c >
/tmp/foo</samp>
-The<samp>/tmp/foo</samp>file is mailed to the [developers
+The <samp>/tmp/foo</samp> file is mailed to the [developers
list](http://httpd.apache.org/lists.html#http-dev) so they can consider the
value/validity of the patch. It is worth making sure your code follows the
Apache style, as described in the [style guide](styleguide.html).
@@ -93,16 +93,16 @@ developer checks the changes into the re
# SVN Subtrees #
-There are several different branches under the<samp>httpd</samp>subtree in
+There are several different branches under the <samp>httpd</samp> subtree in
the Apache SVN repository that pertain to the different releases. The top
level can be perused with the [SVN
ViewCVS](http://svn.apache.org/viewcvs.cgi/) pages. The main subtrees
-pertaining to the<samp>httpd</samp>server source are:
+pertaining to the <samp>httpd</samp>server source are:
## httpd-2.2 ##
To create a directory tree containing the 2.2 sources, and call
-it<samp>httpd-2.2</samp>, change your current directory to the *parent* of
+it <samp>httpd-2.2</samp>, change your current directory to the *parent* of
the tree and then check the 2.2 sources out as follows:
<pre>
% cd /usr/local/apache
@@ -112,7 +112,7 @@ the tree and then check the 2.2 sources
## httpd-2.4 ##
To create a directory tree containing the 2.4 sources, and call
-it<samp>httpd-2.4</samp>, change your current directory to the *parent* of
+it <samp>httpd-2.4</samp>, change your current directory to the *parent* of
the tree and then check the 2.4 sources out as follows:
<pre>
% cd /usr/local/apache
@@ -123,7 +123,7 @@ the tree and then check the 2.4 sources
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:
+it <samp>httpd-trunk</samp>, checkout as follows:
<pre>
% cd /usr/local/apache
% svn checkout http://svn.apache.org/repos/asf/httpd/httpd/trunk
@@ -132,16 +132,16 @@ httpd-trunk</pre>
## httpd-site ##
This subtree contains the files that live
-at<samp>http://httpd.apache.org/</samp>. The directory on the host that
+at <samp>http://httpd.apache.org/</samp>. The directory on the host that
maps to that URL is actually a set of checked-out working copies of the SVN
files.
The SVN URL
-is<samp>https://svn.apache.org/repos/asf/httpd/site/trunk/docs</samp>.
+is <samp>https://svn.apache.org/repos/asf/httpd/site/trunk/docs</samp>.
<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 **that** , 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 *directories* (as opposed to files) are not maintained in
synch with the SVN files automatically. They are manually updated from SVN
@@ -151,22 +151,22 @@ group discussion.
## httpd-dist ##
-Like the<samp>httpd-site</samp>subtree, this one is used to maintain the
+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
+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
subtree. However, since this is a distribution directory, we only have the
surrounding documentation and control files checked into this subtree --
the actual tarballs are simply copied to www.apache.org.
The SVN URL
-is<samp>https://svn.apache.org/repos/asf/httpd/httpd/dist</samp>.
+is <samp>https://svn.apache.org/repos/asf/httpd/httpd/dist</samp>.
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 [Release
Guidelines](release.html) page.
|
