INN commit: trunk/doc/pod (4 files)

[INN Commit]

    Date: Sunday, March 14, 2010 @ 13:43:21
  Author: iulius
Revision: 8994

Better wording, and a POD typo.

Modified:
  trunk/doc/pod/innd.pod
  trunk/doc/pod/install.pod
  trunk/doc/pod/news.pod
  trunk/doc/pod/readers.conf.pod

------------------+
 innd.pod         |   12 ++++++------
 install.pod      |    2 +-
 news.pod         |    6 ++++--
 readers.conf.pod |    5 ++++-
 4 files changed, 15 insertions(+), 10 deletions(-)

Modified: innd.pod
===================================================================
--- innd.pod	2010-03-14 20:41:19 UTC (rev 8993)
+++ innd.pod	2010-03-14 20:43:21 UTC (rev 8994)
@@ -402,12 +402,12 @@
 
 The fourth field indicates whether the article was accepted or not.  If it
 is a plus sign, then the article was accepted.  If it is the letter C<j>,
-then the article was accepted, but all of the newsgroups to which the
-article was posted were set to status C<j> in the F<active> file (or not listed
-in the F<active> file and I<wanttrash> was set in F<inn.conf>) so the article
-was filed into the C<junk> newsgroup.  In both of these cases, the article
-has been accepted and the C<site ...> field contains the space-separated
-list of sites to which the article is being sent.
+then the article was accepted, providing all of the newsgroups to which
+the article was posted were set to status C<j> in the F<active> file (or
+not listed in the F<active> file and I<wanttrash> was set in F<inn.conf>),
+and then the article was filed into the C<junk> newsgroup.  In both of these
+cases, the article has been accepted and the C<site ...> field contains
+the space-separated list of sites to which the article is being sent.
 
 If the fourth field is the letter C<c>, then a cancel message was accepted
 before the original article arrived, and a history entry for the cancelled

Modified: install.pod
===================================================================
--- install.pod	2010-03-14 20:41:19 UTC (rev 8993)
+++ install.pod	2010-03-14 20:43:21 UTC (rev 8994)
@@ -649,7 +649,7 @@
 your MANPATH environment variable; otherwise, you may have to use a
 command like:
 
-    man -M I<pathnews in inn.conf>/share/man inn.conf
+    man -M <pathnews in inn.conf>/share/man inn.conf
 
 to see the inn.conf(5) man page (for example).
 

Modified: news.pod
===================================================================
--- news.pod	2010-03-14 20:41:19 UTC (rev 8993)
+++ news.pod	2010-03-14 20:43:21 UTC (rev 8994)
@@ -84,8 +84,10 @@
 
 =item *
 
-B<nnrpd> no longer differentiates IHAVE from POST.  Articles injected with
-IHAVE are now treated as though they were injected with POST.
+B<nnrpd> no longer differentiates IHAVE from POST.  Articles injected
+with IHAVE are now treated as though they were injected with POST.
+It means that if the previous behaviour of IHAVE was expected, B<innd>
+should handle itself the connection instead of B<nnrpd>.
 
 =back
 

Modified: readers.conf.pod
===================================================================
--- readers.conf.pod	2010-03-14 20:41:19 UTC (rev 8993)
+++ readers.conf.pod	2010-03-14 20:43:21 UTC (rev 8994)
@@ -408,7 +408,10 @@
 
 The client may inject articles with IHAVE.  Note that in order to inject
 articles with the IHAVE command, the user must also have POST permission
-(the C<P> option).
+(the C<P> option).  Articles injected with IHAVE are treated as though
+they were injected with POST, that is to say such articles must not
+have been previously injected (they must not contain headers like
+Injection-Info:).
 
 =item A