changeset 80361:f3cf83f6f6ed

* gnus.texi (Gnus Development): Clarify difference between ding and gnu.emacs.gnus. (MIME Commands, Using MIME, RSS): Fix markup. * gnus-faq.texi ([8.4]): Ditto.
author Reiner Steib <Reiner.Steib@gmx.de>
date Fri, 21 Mar 2008 21:00:45 +0000
parents 4f1a3c09c06a
children db96eae9d737
files man/ChangeLog man/gnus-faq.texi man/gnus.texi
diffstat 3 files changed, 42 insertions(+), 31 deletions(-) [+]
line wrap: on
line diff
--- a/man/ChangeLog	Thu Mar 20 14:17:21 2008 +0000
+++ b/man/ChangeLog	Fri Mar 21 21:00:45 2008 +0000
@@ -1,3 +1,11 @@
+2008-03-21  Reiner Steib  <Reiner.Steib@gmx.de>
+
+	* gnus.texi (Gnus Development): Clarify difference between ding and
+	gnu.emacs.gnus.
+	(MIME Commands, Using MIME, RSS): Fix markup.
+
+	* gnus-faq.texi ([8.4]): Ditto.
+
 2008-03-20  Reiner Steib  <Reiner.Steib@gmx.de>
 
 	* gnus.texi (Emacsen): Remove obsolete stuff.
--- a/man/gnus-faq.texi	Thu Mar 20 14:17:21 2008 +0000
+++ b/man/gnus-faq.texi	Fri Mar 21 21:00:45 2008 +0000
@@ -2126,22 +2126,23 @@
 
 @subsubheading Answer
 
-There's the newsgroup gnu.emacs.gnus
-(also available as
-@uref{http://dir.gmane.org/gmane.emacs.gnus.user, 
-gmane.emacs.gnus.user})
-which deals with general Gnus questions.
+There's the newsgroup gnu.emacs.gnus (also available as
+@uref{http://dir.gmane.org/gmane.emacs.gnus.user,
+gmane.emacs.gnus.user}) which deals with general Gnus questions.  If you
+have questions about development versions of Gnus, you should better ask
+on the ding mailing list, see below.
+
+If you want to stay in the big8,
+news.software.newssreaders is also read by some Gnus
+users (but chances for qualified help are much better in
+the above groups). If you speak German, there's
+de.comm.software.gnus.
+
 The ding mailing list (ding@@gnus.org) deals with development of
 Gnus. You can read the ding list via NNTP, too under the name
 @uref{http://dir.gmane.org/gmane.emacs.gnus.general, 
 gmane.emacs.gnus.general} from news.gmane.org.
 
-If you want to stay in the big8,
-news.software.newssreaders is also read by some Gnus
-users (but chances for qualified help are much better in
-the above groups) and if you speak German, there's
-de.comm.software.gnus.
-
 @node [8.5]
 @subsubheading Question 8.5
 
--- a/man/gnus.texi	Thu Mar 20 14:17:21 2008 +0000
+++ b/man/gnus.texi	Fri Mar 21 21:00:45 2008 +0000
@@ -9511,7 +9511,7 @@
 @item gnus-mime-display-multipart-related-as-mixed
 Display "multipart/related" parts as "multipart/mixed".
 
-If displaying "text/html" is discouraged, see
+If displaying @samp{text/html} is discouraged, see
 @code{mm-discouraged-alternatives}, images or other material inside a
 "multipart/related" part might be overlooked when this variable is
 @code{nil}.  @ref{Display Customization, Display Customization, ,
@@ -11153,7 +11153,7 @@
 @item i (Article)
 @kindex i (Article)
 Insert the contents of the @acronym{MIME} object into the buffer
-(@code{gnus-mime-inline-part}) as text/plain.  If given a prefix, insert
+(@code{gnus-mime-inline-part}) as @samp{text/plain}.  If given a prefix, insert
 the raw contents without decoding.  If given a numerical prefix, you can
 do semi-manual charset stuff (see
 @code{gnus-summary-show-article-charset-alist} in @ref{Paging the
@@ -16310,7 +16310,7 @@
 (add-to-list 'nnmail-extra-headers nnrss-url-field)
 @end lisp
 
-Even if you have added @code{"text/html"} to the
+Even if you have added @samp{text/html} to the
 @code{mm-discouraged-alternatives} variable (@pxref{Display
 Customization, ,Display Customization, emacs-mime, The Emacs MIME
 Manual}) since you don't want to see @acronym{HTML} parts, it might be
@@ -25592,26 +25592,22 @@
 @subsection Gnus Development
 
 Gnus is developed in a two-phased cycle.  The first phase involves much
-discussion on the @samp{ding@@gnus.org} mailing list, where people
+discussion on the development mailing list @samp{ding@@gnus.org}, where people
 propose changes and new features, post patches and new back ends.  This
 phase is called the @dfn{alpha} phase, since the Gnusae released in this
 phase are @dfn{alpha releases}, or (perhaps more commonly in other
 circles) @dfn{snapshots}.  During this phase, Gnus is assumed to be
 unstable and should not be used by casual users.  Gnus alpha releases
-have names like ``Red Gnus'' and ``Quassia Gnus''.
-
-After futzing around for 50-100 alpha releases, Gnus is declared
+have names like ``Oort Gnus'' and ``No Gnus''.  @xref{Gnus Versions}.
+
+After futzing around for 10-100 alpha releases, Gnus is declared
 @dfn{frozen}, and only bug fixes are applied.  Gnus loses the prefix,
-and is called things like ``Gnus 5.6.32'' instead.  Normal people are
+and is called things like ``Gnus 5.10.1'' instead.  Normal people are
 supposed to be able to use these, and these are mostly discussed on the
-@samp{gnu.emacs.gnus} newsgroup.
-
-@cindex Incoming*
-@vindex mail-source-delete-incoming
-Some variable defaults differ between alpha Gnusae and released Gnusae,
-in particular, @code{mail-source-delete-incoming}.  This is to prevent
-lossage of mail if an alpha release hiccups while handling the mail.
-@xref{Mail Source Customization}.
+@samp{gnu.emacs.gnus} newsgroup.  This newgroup is mirrored to the
+mailing list @samp{info-gnus-english@@gnu.org} which is carried on Gmane
+as @samp{gmane.emacs.gnus.user}.  These releases are finally integrated
+in Emacs.
 
 The division of discussion between the ding mailing list and the Gnus
 newsgroup is not purely based on publicity concerns.  It's true that
@@ -25624,10 +25620,16 @@
 usually keep up with these rapid changes, while people on the newsgroup
 can't be assumed to do so.
 
-@c FIXME:
-@c ding = gmane.emacs.gnus.general
-@c newsgroup = gnu.emacs.gnus = gmane.emacs.gnus.user = info-gnus-english
-
+So if you have problems with or questions about the alpha versions,
+direct those to the ding mailing list @samp{ding@@gnus.org}.  This list
+is also available on Gmane as @samp{gmane.emacs.gnus.general}.
+
+@cindex Incoming*
+@vindex mail-source-delete-incoming
+Some variable defaults differ between alpha Gnusae and released Gnusae,
+in particular, @code{mail-source-delete-incoming}.  This is to prevent
+lossage of mail if an alpha release hiccups while handling the mail.
+@xref{Mail Source Customization}.
 
 @node Contributors
 @subsection Contributors