From 6a1d227e4ee199bea2c8ba5bc01b7ece6da5e75b Mon Sep 17 00:00:00 2001
From: Tomas Heinrich <theinric@redhat.com>
Date: Thu, 23 Jul 2015 11:30:13 +0200
Subject: [PATCH] Various corrections to the HTML documentation
Provided by Stephen Wadeley.
---
doc/features.html | 5 +--
doc/free_support.html | 12 +++---
doc/history.html | 8 +---
doc/index.html | 29 +++++++-------
doc/manual.html | 89 ++++++++++++++++++-------------------------
doc/rsyslog_conf_actions.html | 2 +-
doc/troubleshoot.html | 20 +++++-----
doc/version_naming.html | 8 ++--
8 files changed, 76 insertions(+), 97 deletions(-)
diff --git a/doc/features.html b/doc/features.html
index 626ff65..8fc2802 100644
--- a/doc/features.html
+++ b/doc/features.html
@@ -28,7 +28,7 @@ OpenTDS (MS SQL, Sybase), SQLLite, Ingres, Oracle, and mSQL via libdbi,
a database abstraction layer (almost as good as native)</li>
<li>native support for <a href="ommail.html">sending
mail messages</a> (first seen in 3.17.0)</li>
-<li>support for (plain) tcp based syslog - much better
+<li>support for (plain) TCP based syslog - much better
reliability</li>
<li>support for sending and receiving compressed syslog messages</li>
<li>support for on-demand on-disk spooling of messages that can
@@ -141,9 +141,6 @@ large number of applications. You may also read my blog post on the
future of liblogging, which contains interesting information about the <a href="http://rgerhards.blogspot.com/2007/09/where-is-liblogging-heading-to.html">
future of RFC 3195 in rsyslog</a>.</li>
</ul>
-<p>To see when each feature was added, see the
-<a href="http://www.rsyslog.com/Topic4.phtml">rsyslog
-change log</a> (online only).</p>
<p>[<a href="manual.html">manual index</a>]
[<a href="rsyslog_conf.html">rsyslog.conf</a>]
diff --git a/doc/free_support.html b/doc/free_support.html
index 182a82c..4e33102 100644
--- a/doc/free_support.html
+++ b/doc/free_support.html
@@ -16,16 +16,16 @@ system forward.
with a solution (but rather a link to this page ;)). I hope this does not offend you. The
reason is quite simple: If I do personal support, you gain some advantage without
contributing something back. Think about it: if you ask your question on the public
-forum or mailing list, other with the same problem can you and, most importantly, even
+forum or mailing list, others with the same problem can help you and, most importantly, even
years later find your post (and the answer) and get the problem solved. So by
-solving your issue in public, you help create a great community ressource and also
+solving your issue in public, you help create a great community resources and also
help your fellow users finding solutions quicker. In the long term, this
also contributes to improved code because the more questions users can find
solutions to themselves, the fewer I need to look at.
-<p>But it comes even better: the rsyslog community is much broader than Rainer ;) - there
-are helpful other members hanging around at the public places. They often answer
+<p>But it becomes even better: the rsyslog community is much broader than Rainer ;) - there
+are other helpful members hanging around at the public places. They often answer
questions, so that I do not need to look at them (btw, once again a big "thank you", folks!).
-And, more important, those folks have different background than me. So they often
+And, more important, those folks have a different background than me. So they often
either know better how to solve your problem (e.g. because it is distro-specific)
or they know how to better phrase it (after all, I like abstract terms and concepts ;)).
So you do yourself a favor if you use the public places.
@@ -36,7 +36,7 @@ mailing lists, the
<a href="http://lists.adiscon.net/mailman/listinfo/rsyslog">rsyslog mailing list</a>
also offers excellent advise.
<p><b>Don't like to post your question in a public place?</b> Well, then you should
-consider purchasing <a href="professional_support.html">rsyslog professional support</a>.
+consider purchasing <a href="http://www.rsyslog.com/professional-services/">rsyslog professional support</a>.
The fees are very low and help fund the project. If you use rsyslog seriously inside
a corporate environment, there is no excuse for not getting one of the support
packages ;)
diff --git a/doc/history.html b/doc/history.html
index 57b6400..e3c12e3 100644
--- a/doc/history.html
+++ b/doc/history.html
@@ -105,7 +105,7 @@ resulting in loadable input modules, now running on a separate thread each.</p><
<b>January, 2nd 2008</b>, rsyslog 1.21.2 is re-released as rsyslog v2.0.0
stable. This is a major milestone as far as the stable build is concerned. v3 is
not yet officially announced. Other than the stable v2 build, v3 will not be
-backwards compatibile (including missing compatibility to stock sysklogd) for
+backwards compatible (including missing compatibility to stock sysklogd) for
quite a while. Config file changes are required and some command line options do
no longer work due to the new design.</p><p>On <span style="font-weight: bold;">January, 31st 2008</span>
the new massively-multithreaded queue engine was released for the first
@@ -137,11 +137,7 @@ namely anonymization support, as well as log file signing and
encryption capabilities.
<p>Be sure to visit Rainer's <a href="http://rgerhards.blogspot.com/">syslog blog</a>
-to get some more insight into the development and futures of rsyslog and syslog in general.
+to get some more insight into the development and features of rsyslog and syslog in general.
Don't be shy to post to either the blog or the
<a href="http://www.rsyslog.com/PNphpBB2.phtml">rsyslog forums</a>.</p>
-<h2>Some useful links</h2>
-<ul>
- <li><a href="http://www.rsyslog.com/Topic4.phtml">the rsyslog change log</a></li>
-</ul>
</body></html>
diff --git a/doc/index.html b/doc/index.html
index d753e2e..c8172f3 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -6,26 +6,27 @@
is an enhanced syslogd suitable both for small systems as
well as large enterprises.</b>
<p>This page provide a few quick pointers which hopefully make your
-experience with rsyslog a pleasant one. These are
+experience with rsyslog a pleasant one. These are:
<ul>
-<li><b>Most importantly, the <a href="manual.html">rsyslog manual</a></b> - this points to locally
+<li>The <a href="manual.html">rsyslog manual</a> - this points to locally
installed documentation which exactly matches the version you have installed.
It is highly suggested to at least briefly look over these files.
-<li>The <a href="http://www.rsyslog.com">rsyslog web site</a> which offers
-probably every information you'll ever need (ok, just kidding...).
-<li>The <a href="http://www.rsyslog.com/status">project status page</a> provides
-information on current releases
-<li>and the <a href="troubleshoot.html">troubleshooting guide</a> hopefully helps if
-things do not immediately work out
+<li>The <a href="http://www.rsyslog.com">rsyslog web site</a>, which offers
+information for different versions of rsyslog.
+<li>The <a href="troubleshoot.html">troubleshooting guide</a> hopefully helps if
+things do not immediately work out.
</ul>
<p>In general, rsyslog supports plain old syslog.conf format, except that the
config file is now called rsyslog.conf. This should help you get started
-quickly.
-To do the really cool things, though,
-you need to learn a bit about its new features.
+quickly.</p>
+<pa>
The man pages offer a bare minimum of information (and are still quite long). Read the
-<a href="manual.html">html documentation</a> instead.
+built-in <a href="manual.html">html documentation</a> instead.
When you change the configuration, remember to restart rsyslogd, because otherwise
-it will not use your new settings (and you'll end up totally puzzled why this great
-config of yours does not even work a bit...;))
+it will not use your new settings.</p>
+<p>The built-in <a href="history.html">rsyslog history</a>
+page is for you if you would like to learn a little more
+on why there is an rsyslog at all. If you are interested why you should
+care about rsyslog at all, you may want to read Rainer's essay on "<a href="http://rgerhards.blogspot.com/2007/08/why-does-world-need-another-syslogd.html">why
+the world needs another syslogd</a>".</p>
</body></html>
diff --git a/doc/manual.html b/doc/manual.html
index f0fffa8..ecf8cae 100644
--- a/doc/manual.html
+++ b/doc/manual.html
@@ -2,11 +2,11 @@
<html><head><title>rsyslog documentation</title></head>
<body>
<h1>RSyslog - Documentation</h1>
-<p><b><a href="http://www.rsyslog.com/">Rsyslog</a>
-is an enhanced syslogd
+<p><a href="http://www.rsyslog.com/">Rsyslog</a>
+is an enhanced <b>syslogd</b>
supporting, among others, <a href="rsyslog_mysql.html">MySQL</a>,
PostgreSQL, <a href="http://wiki.rsyslog.com/index.php/FailoverSyslogServer">failover
-log destinations</a>, syslog/tcp, fine grain output format
+log destinations</a>, syslog over TCP, fine grain output format
control, high precision timestamps, queued operations and the ability to filter on any message
part.</b>
It is quite compatible to stock sysklogd and can be used as a drop-in
@@ -16,48 +16,37 @@ relay chains while at the same time being very easy to setup for the
novice user. And as we know what enterprise users really need, there are
also <a href="http://www.rsyslog.com/professional-services"> rsyslog
professional services</a> available directly from the source!</p>
-<p><b>Please visit the <a href="http://www.rsyslog.com/sponsors">rsyslog sponsor's page</a>
+<p>Please visit the <a href="http://www.rsyslog.com/sponsors">rsyslog sponsor's page</a>
to honor the project sponsors or become one yourself!</b> We are very grateful for any help towards the
project goals.</p>
-<p><b>This documentation is for version 7.4.7 (v7.4-stable branch) of rsyslog.</b>
-Visit the <i><a href="http://www.rsyslog.com/status">rsyslog status page</a></i></b>
-to obtain current version information and project status.
-</p><p><b>If you like rsyslog, you might
-want to lend us a helping hand. </b>It doesn't require a lot of
+<p><b>This documentation is for version 7.4.7 (v7.4-stable branch) of rsyslog.</b> If you use an older
+version, be sure to use the doc that came with it.</p>
+<p>If you like rsyslog, you might
+want to lend us a helping hand. It doesn't require a lot of
time - even a single mouse click helps. Learn <a href="how2help.html">how to help the rsyslog project</a>.
Due to popular demand, there is now a <a href="rsyslog_ng_comparison.html">side-by-side comparison
between rsyslog and syslog-ng</a>.</p>
-<p>If you are upgrading from rsyslog v2 or stock sysklogd,
-<a href="v3compatibility.html">be sure to read the rsyslog v3 compatibility notes</a>,
-and if you are upgrading from v3, read the
-<a href="v4compatibility.html">rsyslog v4 compatibility notes</a>,
-if you upgrade from v4, read the
-<a href="v5compatibility.html">rsyslog v5 compatibility notes</a>, and
-if you upgrade from v5, read the
-<a href="v6compatibility.html">rsyslog v6 compatibility notes</a>.
-if you upgrade from v6, read the
-<a href="v7compatibility.html">rsyslog v7 compatibility notes</a>.
-<p>Rsyslog will work even
-if you do not read the doc, but doing so will definitely improve your experience.</p>
-<p><b>Follow the links below for the</b></p>
+<p><b>If you are upgrading</b>
<ul>
-<li><a href="troubleshoot.html">troubleshooting rsyslog problems</a></li>
-<li><a href="rsyslog_conf.html">configuration file format (rsyslog.conf)</a></li>
-<li><a href="http://www.rsyslog.com/tool-regex">a regular expression checker/generator tool for rsyslog</a></li>
-<li> <a href="property_replacer.html">property replacer, an important core component</a></li>
-<li><a href="bugs.html">rsyslog bug list</a></li>
+<li>from rsyslog v2 or stock sysklogd,
+<a href="v3compatibility.html">be sure to read the rsyslog v3 compatibility notes</a>,</li>
+<li>if you are upgrading from v3, read the
+<a href="v4compatibility.html">rsyslog v4 compatibility notes</a>,</li>
+<li>if you are upgrading from v4, read the
+<a href="v5compatibility.html">rsyslog v5 compatibility notes</a>,</li>
+<li>if you are upgrading from v5, read the
+<a href="v6compatibility.html">rsyslog v6 compatibility notes</a>, and </li>
+<li>if you are upgrading from v6, read the
+<a href="v7compatibility.html">rsyslog v7 compatibility notes</a>.</li>
+</ul>
+<p><b>The built-in Docs</b></p>
+<ul>
+<li><a href="rsyslog_conf.html">The rsyslog.conf file format and its configuration</a></li>
+<li><a href="property_replacer.html">property replacer, an important core component</a></li>
<li><a href="messageparser.html">understanding rsyslog message parsers</a></li>
<li><a href="generic_design.html">backgrounder on generic syslog application design</a></li>
<li><a href="modules.html">description of rsyslog modules</a></li>
-<li><a href="rsyslog_packages.html">rsyslog packages</a></li>
-</ul>
-<p><b>To keep current on rsyslog development, follow
-<a href="http://twitter.com/rgerhards">Rainer's twitter feed</a>.</b></p>
-<p><b>We have some in-depth papers on</b></p>
-<ul>
-<li><a href="install.html">installing rsyslog</a></li>
-<li><a href="build_from_repo.html">obtaining rsyslog from the source repository</a></li>
-<li><a href="ipv6.html">rsyslog and IPv6</a> (which is fully supported)</li>
+<li><a href="ipv6.html">rsyslog and IPv6</a></li>
<li><a href="rsyslog_secure_tls.html">native TLS encryption for syslog</a></li>
<li><a href="multi_ruleset.html">using multiple rule sets in rsyslog</a></li>
<li><a href="rsyslog_stunnel.html">ssl-encrypting syslog with stunnel</a></li>
@@ -69,36 +58,31 @@ if you do not read the doc, but doing so will definitely improve your experience
php-syslog-ng with rsyslog</a></li>
<li><a href="rsyslog_recording_pri.html">recording
the syslog priority (severity and facility) to the log file</a></li>
-<li><a href="http://www.rsyslog.com/Article19.phtml">preserving
-syslog sender over NAT</a> (online only)</li>
<li><a href="gssapi.html">an overview and howto of rsyslog gssapi support</a></li>
<li><a href="debug.html">debug support in rsyslog</a></li>
+<li><a href="troubleshoot.html">troubleshooting rsyslog problems</a></li>
+<li><a href="bugs.html">rsyslog bug list</a></li>
<li>Developer Documentation
<ul>
+ <li><a href="rsyslog_packages.html">rsyslog packages</a></li>
+ <li><a href="install.html">installing rsyslog</a></li>
+ <li><a href="build_from_repo.html">obtaining rsyslog from the source repository</a></li>
<li><a href="build_from_repo.html">building rsyslog from the source repository</a></li>
<li><a href="dev_oplugins.html">writing rsyslog output plugins</a></li>
<li><a href="dev_queue.html">the rsyslog message queue object (developer's view)</a></li>
</ul></li>
</ul>
-<p>Our <a href="history.html">rsyslog history</a>
-page is for you if you would like to learn a little more
-on why there is an rsyslog at all. If you are interested why you should
-care about rsyslog at all, you may want to read Rainer's essay on "<a href="http://rgerhards.blogspot.com/2007/08/why-does-world-need-another-syslogd.html">why
-the world needs another syslogd</a>".</p>
-<p>Documentation is added continuously. Please note that the
-documentation here
-matches only the current version of rsyslog. If you use an older
-version, be sure to use the doc that came with it.</p>
+
<p><b>You can also browse the following online resources:</b></p>
<ul>
+<li><a href="http://www.rsyslog.com/Article19.phtml">preserving
+syslog sender over NAT</a></li>
+<li><a href="http://www.rsyslog.com/tool-regex">a regular expression checker/generator tool for rsyslog</a></li>
<li>the <a href="http://wiki.rsyslog.com/">rsyslog
wiki</a>, a community resource which includes <a href="http://wiki.rsyslog.com/index.php/Configuration_Samples">rsyslog configuration examples</a></li>
-<li><a href="http://www.rsyslog.com/module-Static_Docs-view-f-manual.html.phtml">rsyslog
-online documentation (most current version only)</a></li>
<li><a href="http://kb.monitorware.com/rsyslog-f40.html">rsyslog discussion forum - use this for technical support</a></li>
<li><a href="http://www.rsyslog.com/Topic8.phtml">rsyslog video tutorials</a></li>
-<li><a href="http://www.rsyslog.com/Topic4.phtml">rsyslog change log</a></li>
<li><a href="http://www.rsyslog.com/Topic3.phtml">rsyslog FAQ</a></li>
<li><a href="http://www.monitorware.com/en/syslog-enabled-products/">syslog device configuration guide</a> (off-site)</li>
<li><a href="http://www.rsyslog.com/PNphpBB2.phtml">rsyslog discussion forum - use this for technical support</a></li>
@@ -111,7 +95,8 @@ may find
<a href="http://blog.gerhards.net/">blog</a> an
interesting read (filter on syslog and rsyslog tags).
Or meet <a href="http://www.facebook.com/people/Rainer-Gerhards/1349393098">Rainer Gerhards at Facebook</a>
-or <a href="https://plus.google.com/112402185904751517878/posts">Google+</a>.
+or <a href="https://plus.google.com/112402185904751517878/posts">Google+</a>.</p>
+<pa>
If you would like to use rsyslog source code inside your open source project, you can do that without
any restriction as long as your license is GPLv3 compatible. If your license is incompatible to GPLv3,
you may even be still permitted to use rsyslog source code. However, then you need to look at the way
@@ -119,5 +104,5 @@ you may even be still permitted to use rsyslog source code. However, then you ne
<p>Feedback is always welcome, but if you have a support question, please do not
mail Rainer directly (<a href="free_support.html">why not?</a>) - use the
<a href="http://lists.adiscon.net/mailman/listinfo/rsyslog">rsyslog mailing list</a>
-or <a href="http://kb.monitorware.com/rsyslog-f40.html">rsyslog formum</a> instead.
+or <a href="http://kb.monitorware.com/rsyslog-f40.html">rsyslog forum</a> instead.
</body></html>
diff --git a/doc/rsyslog_conf_actions.html b/doc/rsyslog_conf_actions.html
index 50b13a0..c0c29c7 100644
--- a/doc/rsyslog_conf_actions.html
+++ b/doc/rsyslog_conf_actions.html
@@ -5,7 +5,7 @@
<a href="rsyslog_conf.html">back</a>
<h2>Actions</h2>
Action object describe what is to be done with a message. They are
-implemented via <a href="rsyslog_conf_modules.html#om">outpout modules</a>.
+implemented via <a href="rsyslog_conf_modules.html#om">output modules</a>.
<p>The action object has different parameters:
<ul>
<li>those that apply to all actions and are action specific. These
diff --git a/doc/troubleshoot.html b/doc/troubleshoot.html
index a0303a2..ef3a4b1 100644
--- a/doc/troubleshoot.html
+++ b/doc/troubleshoot.html
@@ -4,8 +4,8 @@
<h2>troubleshooting rsyslog</h2>
<p><b>Having trouble with <a href="http://www.rsyslog.com">rsyslog</a>?</b>
This page provides some tips on where to look for help and what to do
-if you need to ask for assistance. This page is continously being expanded.
-<p>Useful troubleshooting ressources are:
+if you need to ask for assistance. This page is continuously being expanded.
+<p>Useful troubleshooting resources are:
<ul>
<li>The <a href="http://www.rsyslog.com/doc">rsyslog documentation</a> - note that the online version always covers
the most recent development version. However, there is a version-specific
@@ -19,7 +19,7 @@ is a rsyslog-doc package, that often needs to be installed separately.
<p>A common trouble source are <a href="syslog_parsing.html">ill-formed syslog messages</a>, which
lead to to all sorts of interesting problems, including malformed hostnames and dates.
Read the quoted guide to find relief. A common symptom is that the %HOSTNAME% property is
-used for generating dynafile names, but some glibberish shows up. This is caused by the
+used for generating dynafile names, but some gibberish shows up. This is caused by the
malformed syslog messages, so be sure to read the
<a href="syslog_parsing.html">guide</a> if you face that problem. Just let me add that the
common work-around is to use %FROMHOST% or %FROMHOST-IP% instead. These do not take the
@@ -28,7 +28,7 @@ the socket layer). Of course, this does not work over NAT or relay chains, where
only cure is to make sure senders emit well-formed messages.
<p><b>Configuration Problems</b>
<p>Rsyslog 3.21.1 and above has been enhanced to support extended configuration checking.
-It offers a special command line switch (-N1) that puts it into "config verfication mode".
+It offers a special command line switch (-N1) that puts it into "config verification mode".
In that mode, it interprets and check the configuration file, but does not startup. This
mode can be used in parallel to a running instance of rsyslogd.
<p>To enable it, run rsyslog interactively as follows:
@@ -56,7 +56,7 @@ The mailing list is probably a good place for complex questions.
</ul>
<p><b>Debug Log</b>
<p>If you ask for help, there are chances that we need to ask for an rsyslog debug log.
-The debug log is a detailled report of what rsyslog does during processing. As such, it may
+The debug log is a detailed report of what rsyslog does during processing. As such, it may
even be useful for your very own troubleshooting. People have seen things inside their debug
log that enabled them to find problems they did not see before. So having a look at the
debug log, even before asking for help, may be useful.
@@ -89,7 +89,7 @@ meaningless value. <b>Do not delete the lines</b>, as this renders the debug log
unusable (and makes Rainer quite angry for wasted time, aka significantly reduces the chance
he will remain motivated to look at your problem ;)). For the same reason, make sure
whatever you change is changed consistently. Really!
-<p>While most debug log files are moderately large, some can get quite to extremly large.
+<p>While most debug log files are moderately large, some can get quite to extremely large.
For those on the larger side, it is a good idea to zip them. If the file is less than
around 100KiB, it's probably not necessary.
<p>A good place to post your debug log is at the
@@ -99,9 +99,9 @@ various common formats, but rejects others for security reasons. The zip, txt, a
are definitely permitted, so it probably is a good idea to use one of them. For others, please
simply try and revert to another format if the forum doesn't like what you used.
<p>
-Please note that all information in your debug file is publically visiable.
+Please note that all information in your debug file is publicly visible.
If this is not acceptable for you, you are probably a
-candidate for a <a href="professional_support.html">commercial support contract</a>. Free support
+candidate for a <a href="http://www.rsyslog.com/professional-services/">commercial support contract</a>. Free support
comes without any guarantees, include no guarantee on confidentiality
[aka "we don't want to be sued for work were are not even paid for ;)].
<b>So if you submit debug logs, do so at your sole risk</b>. By submitting them, you accept
@@ -115,11 +115,11 @@ you may see a serious problem during deployments in demanding, non-standard, env
(hopefully not with a stable version, but chances are good you'll run into troubles with
the development versions).
<p>Active support from the user base is very important to help us track down those things.
-Most often, serious problems are the result of some memory misadressing. During development,
+Most often, serious problems are the result of some memory misaddressing. During development,
we routinely use valgrind, a very well and capable memory debugger. This helps us to create
pretty clean code. But valgrind can not detect everything, most importantly not code pathes
that are never executed. So of most use for us is information about aborts and abort locations.
-<p>Unforutnately, faults rooted in adressing errors typically show up only later, so the
+<p>Unfortunately, faults rooted in addressing errors typically show up only later, so the
actual abort location is in an unrelated spot. To help track down the original spot,
<a href="http://www.gnu.org/software/hello/manual/libc/Heap-Consistency-Checking.html">libc
later than 5.4.23 offers support</a> for finding, and possible temporary relief from it,
diff --git a/doc/version_naming.html b/doc/version_naming.html
index 3bfa19b..fe59d19 100644
--- a/doc/version_naming.html
+++ b/doc/version_naming.html
@@ -23,7 +23,7 @@ maybe around once a year. A major version increment has important
implications from the support side: without support contracts, the
current major version's last stable release and the last stable release
of the version immediately below it are supported (Adiscon, the rsyslog
-sponsor, offers <a href="professional_support.html">support contracts</a> covering all other versions).</p>
+sponsor, offers <a href="http://www.rsyslog.com/professional-services/">support contracts</a> covering all other versions).</p>
<p>The <span style="font-weight: bold;">minor</span> version is
incremented whenever a non-trivial new feature is planned to be added.
Triviality of a feature is simply determined by time estimated to
@@ -57,7 +57,7 @@ more if someone has asked for the feature). So we do not like to wait
for the original focus feature to be ready (what could take maybe three
more weeks). As a result, we release the new features. But that version
will also include partial code of the focus feature. Typically this
-doesn't hurt as long as noone tries to use it (what of course would
+doesn't hurt as long as no one tries to use it (what of course would
miserably fail). But still, part of the new code is already in it. When
we release such a "minor-feature enhanced" but "focus-feature not yet
completed" version, we need a way to flag it. In current thinking, that
@@ -85,14 +85,14 @@ the next minor development version while the previous minor version is
still a -rc because it is not yet considered sufficiently stable.</p><p>Note: <span style="font-weight: bold;">the
absence of the -devstate part indicates that a release is stable.
Following the same logic, any release with a -devstate part is unstable.</span></p><p>A quick sample: </p><p>4.0.0
-is the stable release. We begin to implement relp, moving to
+is the stable release. We begin to implement RELP, moving to
major.minor to 4.1. While we develop it, someone requests a trivial
feature, which we implement. We need to release, so we will have
4.1.0-mf0. Another new feature is requested, move to 4.1.0-mf2. A first
version of RELP is implemented: 4.1.0-rc0. A new trivial feature is
implemented: 4.1.0-rc1. Relp is being enhanced: 4.1.0-rc2. We now feel
RELP is good enough for the time being and begin to implement TLS on
-plain /Tcp syslog: logical increment to 4.2. Now another new feature in
+plain TCP syslog: logical increment to 4.2. Now another new feature in
that tree: 4.2.0-mf0. Note that we now have 4.0.0 (stable) and
4.1.0-rc2 and 4.1.0-mf0 (both devel). We find a big bug in RELP coding.
Two new releases: 4.1.0-rc3, 4.2.0-mf1 (the bug fix acts like a
--
1.9.3