Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Juri Linkov <juri@jurta.org>
Cc: Katsumi Yamaoka <yamaoka@jpl.org>,
	rms@gnu.org, ding@gnus.org, emacs-devel@gnu.org
Subject: Directory doc/gnus in Emacs CVS (was: Splitting gnus.texi)
Date: Wed, 26 Sep 2007 20:14:45 +0200	[thread overview]
Message-ID: <v9bqbpqooa.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87bqbpsqc7.fsf@jurta.org> (Juri Linkov's message of "Wed, 26 Sep 2007 11:55:52 +0300")

On Wed, Sep 26 2007, Juri Linkov wrote:

>> I can agree with splitting if it is very useful to users, though.
>
> This is intended for developers.  So if developers think this is
> not useful then there is no need to split it.
>
> I proposed splitting only because source files for the Emacs manual are
> split into several texi files.  However, I see no clear benefits
> of splitting.  

Me neither.

> Rather we could take the suggestion of Reiner and put gnus-coding,
> gnus-news, gnus-faq, gnus, message, sasl, emacs-mime, pgg and sieve
> into a new `gnus' subdirectory.

For the record some explanations about these files:

  - gnus*.el are (parts of) core Gnus manuals. 
  
  - Message:(message).         Composing messages.
  - Emacs-MIME:(emacs-mime).   Composing messages; MIME-specific parts.
  
  Both are supposed to be independent from Gnus.  Alas it they are not
  anymore.  emacs-mime is also used by MH-E.  AFAICS, the MH-E manual
  describes the relevant MH-E specific stuff  and has some references to
  the emacs-mime and Gnus manual.
  
  - Sieve:(sieve).             Managing Sieve scripts in Emacs.
  - PGG:(pgg).                 PGP/MIME with Gnus.
  - SASL:(sasl).               SASL authentication in Emacs.
  
  These are independent from Gnus.

It would be fine with me to include those in a separate doc/gnus
directory.  But maybe the authors Simon Josefsson (sieve) and Daiki
Ueno (pgg and sasl) would prefer to have them in doc/misc.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

  reply	other threads:[~2007-09-26 18:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1IPj9V-0003Yo-MM@fencepost.gnu.org>
     [not found] ` <mxejhjdrqs.fsf@fencepost.gnu.org>
     [not found]   ` <E1IRYNh-0003dG-Sc@fencepost.gnu.org>
     [not found]     ` <jer6lh2f4e.fsf@sykes.suse.de>
     [not found]       ` <E1ISGc3-000624-G9@fencepost.gnu.org>
     [not found]         ` <izlkbnk2us.fsf@fencepost.gnu.org>
     [not found]           ` <87fy1v36be.fsf@neutrino.caeruleus.net>
     [not found]             ` <u3axvv8rp.fsf@gnu.org>
     [not found]               ` <E1ISbWd-00074O-HB@fencepost.gnu.org>
     [not found]                 ` <87fy1ut4hp.fsf@jurta.org>
2007-09-24 17:10                   ` Splitting gnus.texi (was: Split man directory) Reiner Steib
2007-09-25 10:44                     ` Richard Stallman
2007-09-26  0:23                       ` Splitting gnus.texi Katsumi Yamaoka
2007-09-26  6:07                         ` Reiner Steib
2007-09-30 20:50                           ` Giorgos Keramidas
2007-09-30 21:34                             ` Reiner Steib
2007-09-30 21:46                               ` Giorgos Keramidas
2007-09-26  8:55                         ` Juri Linkov
2007-09-26 18:14                           ` Reiner Steib [this message]
2007-10-20 22:33                             ` Directory doc/gnus in Emacs CVS Bill Wohler
2007-10-21  9:37                               ` Reiner Steib
2007-10-21 16:26                               ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=v9bqbpqooa.fsf_-_@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=rms@gnu.org \
    --cc=yamaoka@jpl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).